feat: add the ability to directly encrypt a specified FILE into OUTPUT in the current directory #299
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
Rexcrazy804
changed the title
|
forgot to mention that the file name must be explicitly specified using the
|
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 enables agenix to leverage the ability to encrypt/decrypt more than just plain text data. I haven't done any sort of rigorous testing (besides testing it with my own config) YET but I plan on doing so. Any advice regarding the same is welcome.
That said, I am uncertain whether this still falls in the scope of "secrets" deployment, so I am open to discuss this further or render this pr as beyond the scope of the project.