We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A dry run mode would be very handy. Especially because secrets in secretsmanager take 7 days to delete.
For example, I'm using the secrets backend and I use this to write.
chamber -b secretsmanager write "service" "datadog" -- "value"
This creates service name with a datadog=value which would be nice to know before writing/updating it.
service
datadog=value
$ chamber -b secretsmanager write --dry-run "service" "datadog" -- "value" dry-run detected Would create "arn:aws:secretsmanager:us-east-1:123456789012:secret:service-??????" with datadog=value
This way, I would then know to do the following
$ chamber -b secretsmanager write --dry-run "service/datadog" "api_key" -- "value" dry-run detected Would create "arn:aws:secretsmanager:us-east-1:123456789012:secret:service/datadog-??????" with api_key=value
The text was updated successfully, but these errors were encountered:
No branches or pull requests
A dry run mode would be very handy. Especially because secrets in secretsmanager take 7 days to delete.
For example, I'm using the secrets backend and I use this to write.
This creates
service
name with adatadog=value
which would be nice to know before writing/updating it.This way, I would then know to do the following
The text was updated successfully, but these errors were encountered: