-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability for Dapr CLI to add/get secrets from secret store component #742
Comments
Pairs with #741 to improve secrets management for Dapr |
I like this idea, but I think it should probably be write only. We add the CLI to simplify adding secrets, that can then only be read by the Dapr secrets API. |
Depends on dapr/dapr#3301 |
I actually think adding the ability to get secrets from the CLI would be a useful inner loop feature. Component scoping can allow CLI access to be disabled in production scenarios |
Also a |
Based on feedback from this morning it sounds like |
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. |
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. |
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions. |
Describe the proposal
Dapr CLI should have a command like
dapr secrets
to add/put secrets from a secret store component. Something like:dapr secrets add --data '{"connectionString":"343ab342c34a2"}'
dapr secrets add --data-file ./mysecrets.json
dapr secrets get --key "connectionString"
With dapr/dapr#3301 the set secret command should work with any secret component.
Without a POST API, the CLI set command add and get commands should interact with the local JSON file created by #741
Release Note
RELEASE NOTE: ADD new
secrets
command to get/set secrets from a local JSON secret storeThe text was updated successfully, but these errors were encountered: