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.
I have noticed, that helmsman supports
hiera-eyaml
with only local PKCS7 keys for secrets. This PR adds support for Google Cloud KMS inhiera-eyaml
.Currently, helmsman only supports
hiera-eyaml
with local PKCS7 keys for secrets. This limits users who want to manage their keys differently.I have made a code changes to add support for
hiera-eyaml-gkms
, which is a plugin forhiera-eyaml
that extends defaulthiera-eyaml
functionalities. This will allow users to encrypt and decrypt secrets using GKMS keys stored in GCP. Users can specify the project id, keyring and crypto-key they are referring to.These change will add a valuable feature to helmsman allowing users to use different method and can be a starting point to include also different cloud providers for
heira-eyaml
.