Rename components directory to resources under .dapr directory

[pravinpushkar]

Describe the proposal

The issue #953 layout a proposal for using resources-path flag with dapr run instead of components-path flag and slowly deprecating it.
In the similar context it would make sense to rename components directory to resources and slowly deprecate components directory use.

Since the components directory is heavily used and exists from beginning so, migrating from components to resources directly should be done in a phased manner.

We can use this issue to discuss different approaches for this issue.

Release Note

RELEASE NOTE:

[pravinpushkar]

@mukundansundar @yaron2 @shubham1172 @msfussell @artursouza

[shubham1172]

Sounds good!

1. When running a dapr init, use resources instead of components.
2. When running dapr run, order of precedence can be resources > components. If components is used, a warning log can be added with a link to the GitHub issue with more details on the deprecation.

[mukundansundar]

Sounds good!

1. When running a dapr init, use resources instead of components.
2. When running dapr run, order of precedence can be resources > components. If components is used, a warning log can be added with a link to the GitHub issue with more details on the deprecation.

Agreed with one small change.
Only when ~/.daor/components is not there, will dapr init create the ~/.dapr/resources folder.
There might be a preexisting ~/.dapr/components if dapr uninstall --all is not used before dapr init

Only when default dir is used, will the deprecation notice be printed i.e. for ~/.dapr/components dir.
Also when --components-path is used, then also a deprecation notice needs to be printed.

[shubham1172]

There might be a preexisting ~/.dapr/components if dapr uninstall --all is not used before dapr init

In this case, shall we warn and copy files to resources?

Also when --components-path is used, then also a deprecation notice needs to be printed.

Out of scope for this issue?

[pravinpushkar]

Out of scope for this issue?

It is being covered in #1012

[pravinpushkar]

Based on the above suggestions -

1. When User just upgrades his dapr cli without uninstalling -> all usage of dapr run --components-path "" will start giving deprecation message but continues to work.
2. User does dapr init after dapr uninstall or dapr uninstall --all -> Create resources directory always and copy the files from components directory if components dir exists.
3. In all cases dapr run without either of the above flags, will default to looking resources dir first then components dir.

[mukundansundar]

Based on the above suggestions -

1. When User just upgrades his dapr cli without uninstalling -> all usage of dapr run --components-path "" will start giving deprecation message but continues to work.
2. User does dapr init after dapr uninstall or dapr uninstall --all -> Create resources directory always and copy the files from components directory if components dir exists.
3. In all cases dapr run without either of the above flags, will default to looking resources dir first then components dir.

this looks good to me.
@yaron2 thoughts?

[pravinpushkar]

/assign

[dapr-bot]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[mukundansundar]

Have triaged this to be completed in 1.11