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.
Sops secret resolver
this adds sops as an extra secret resolver. I've used most(if not all) of the code from the sops ansible collection I've left the original license and copyright notices in place.
Motivation and Context
I'm working on having himl as a data layer for ansible inventory. Using sops as a secret store. It would be great to have this as native usage in sops instead of sprinkling ansible lookups all over.
This might need some more work, but mainly looking here if you're open to making this part of himl?
How Has This Been Tested?
I've tested this with my own key and encrypted files. To reproduce follow the steps from sops, and edit the
examples/secrets/default.yaml
to use the example file and fetch a secret.Screenshots (if appropriate):
Types of changes
Checklist: