Add the option to create a KMS key for signing of pipelines #1366
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wolfeidau
force-pushed
the
feat_add_kms_signing_support
branch
from
0bb7927
to
60c38f7
Compare
wolfeidau
force-pushed
the
feat_add_kms_signing_support
branch
from
0aee15c
to
e4cd1c7
Compare
wolfeidau
force-pushed
the
feat_add_kms_signing_support
branch
from
237638e
to
02740d8
Compare
wolfeidau
force-pushed
the
feat_add_kms_signing_support
branch
from
02740d8
to
e2b6872
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This change adds the option to add a KMS key to the stack for signing and verifying of pipelines. Setting this to a keyspec will create the key and configure all agents to use this key.