KMS Choice and Documentation #20
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR (built on #19 for simple merging):
Secret
YAML tag class that supported custom KMS keys. I later added aSecureString
class (and!SecureString
tag) as a more memorable syntax for adding secrets (all backwards compatible withSecureTag
).git
equivalents. The only alias I left was forplan
as I rarely use git in the CLI sostatus
is not as obvious (to me) asclone
,pull
, andpush
.SSM_NO_DECRYPT
option.This will probably be my last PR for some time (unless I discover a bug or someone needs a behavior tweaked). I dove into this project so we could use it to migrate YAML configs to Parameter Store and continue to maintain those configs on parameter store. At this point, the project does enough of what we need to get back to the migration itself.