Unable to start sidecar when using secrets components with dapr run -f

[bondz]

Expected Behavior

When running the a daprized app using the dapr cli, it should be able to read secrets defined in a configuration

Actual Behavior

The dapr sidecar is never started.

Steps to Reproduce the Problem

See a small repro here - https://github.com/bondz/dapr-secrets

Clone the repo.

cd my-service
npm install

There's a single secret defined in the .dapr/secrets.json file that the app (my-service) reads.

When running the app directly using dapr multi-app run in the root directory, the sidecar is never started.

dapr run -f .

It hangs for a while, eventually errors and exits.

However, if you use vscode and run the app using the launch configuration, passing the config flags directly, it works fine.

[bondz]

When using dapr run -f ., daprd is looking for the file in the my-service directory rather than relative to where dapr run was invoked.

Moving the secret file to the same directory as the service is a workaround.

[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.

[bondz]

Bot comment

[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.

[bondz]

Bot comment

[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.

[bondz]

Bot comment

[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.