Skip to content
This repository has been archived by the owner on Nov 20, 2023. It is now read-only.

Multiple resource paths on dapr 11 - components-path has been deprecated #1603

Open
KrzysztofPajak opened this issue Jul 24, 2023 · 0 comments · May be fixed by #1614
Open

Multiple resource paths on dapr 11 - components-path has been deprecated #1603

KrzysztofPajak opened this issue Jul 24, 2023 · 0 comments · May be fixed by #1614
Labels
bug Something isn't working

Comments

@KrzysztofPajak
Copy link

Hi,
Starting from dapr version 11 we have new feature - support multiple resource paths. Now you can provide multiple resource paths. Example: dapr run --resources-path ./mycomponents --resources-path ./mysubscriptions

After run tye we get message on dapr:
":/dapr/dapr.exe run --app-id core --dapr-grpc-port 50119 --dapr-http-port 50120 --metrics-port 50121 --app-port 5000 --components-path ../.kubernetes/tye/ --log-level debug
[core-dapr_d3fa3ee8-2]: Flag --components-path has been deprecated, This flag is deprecated and will be removed in the future releases. Use "resources-path" flag instead"

When "resources-path" will be available on tye?

@KrzysztofPajak KrzysztofPajak added the bug Something isn't working label Jul 24, 2023
@Phiph Phiph linked a pull request Oct 11, 2023 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant