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
would be good for secrets to be able to be encrypted with a defined kms_id and decrypted where necessary i.e.
kms_id: 'key id here'
dev: some_secret: enc("BASE64 ENCODED SECRET")
So that we can hold specific things in the yaml i.e. root_rds_password or whatnot.
The text was updated successfully, but these errors were encountered:
That's definitely a good idea.
Sorry, something went wrong.
Given you want to use KMS to do this would it be better to use parameter store to store something like this?
If so you can get CF to resolve the secret from parameter store directly https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/dynamic-references.html#dynamic-references-ssm
No branches or pull requests
would be good for secrets to be able to be encrypted with a defined kms_id and decrypted where necessary i.e.
kms_id: 'key id here'
dev:
some_secret: enc("BASE64 ENCODED SECRET")
So that we can hold specific things in the yaml i.e. root_rds_password or whatnot.
The text was updated successfully, but these errors were encountered: