DaprExtension not working with Dapr 0.8.0 ( unable to find components folder)

[mtaghavi2005]

Describe the bug

DaprExtension is not working with newly released version of Dapr (0.8.0).

To Reproduce

1. Clone the tye repository and go to tye\samples\dapr\

cd .\samples\dapr\

2. Update Dapr.AspNetCore package for all project (order, products, store) to 0.8.1
   
3. Reassure that you are using the 0.8.1 runtime version of dapr.

dapr --version
// and upgrade if is necessary
dapr uninstall --all
dapr init --runtime-version 0.8.0

4. Run tye and open dashboard page

 tye run --dashboard

5. In opened dashboard find the store binding address and open it. after clicking any buy button you will get following error:

6. In dashboard everything seems to be alright, but if you go to log details page of one dapr proxy service like "store-dapr" you will find following warning:

Further technical details

After some investigations I found following problem:

According to one of the latest changes (dapr/dapr@8f91634) in Dapr 0.8.0, if --components-path option is not provided, then $HOME/.dapr/component in Linux/MacOS and %USERPROFILE%.dapr\components for Windows will be selected to used as the default components path instead of "./components". But in DaprExtension there is no possibility to provide -components-path in tye.yaml file. (like config or log-level)

• tye tool: 0.3.0-alpha.20318.3+224101f108311b4d38b226eed75d0ec03fa14db1
• dapr CLI: 0.8.0
• dapr runtime: 0.8.0
• OS: Windows 10
• Source code: https://github.com/dotnet/tye/tree/master/samples/dapr

[mtaghavi2005]

Very quick fix :

https://github.com/mtaghavi2005/tye/tree/bugfix/dapr-components-path

If it is applicable, I will submit a PR.
Thank you in advance.

[kimcuhoang]

Since the new release of Dapr will automatically create %UserProfile%\.dapr\components folder. Therefore, we can work around by copying pubsub.yaml and statestore.yaml to this location.

[jkotalik]

I think supporting the components via the extension is fine. @mtaghavi2005 feel free to submit a PR.

I'd think tye shouldn't take an opinion on the components folder though, it should use the default based on the version of dapr used.

[mtaghavi2005]

I think supporting the components via the extension is fine. @mtaghavi2005 feel free to submit a PR.

I'd think tye shouldn't take an opinion on the components folder though, it should use the default based on the version of dapr used.

True, I 'd think the same, but it can just give a chance (providing option via extension) to configure it otherwise won't change the default behavior for dapr.