Add option to skip shell escaping #66
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 pull request adds a flag
--rawto skip shell escaping the values that are being output. The use-case I have for this flag is two-fold:The current escaping is quite aggressive and adds quotes in scenarios where they're not strictly necessary (e.g.
export FOO=bar+bazworks fine but currently gets escaped); adding this flag means more predictable output in scenarios where the user knows that the secrets won't contain any shell-specific special characters.More importantly adding this flag means that ejson2env can now be used on Github Actions to set environment variables (docs) via
ejson2env --raw path/to/secrets.ejson >> "${GITHUB_ENV}". Before this PR, this approach wouldn't work as Github Actions doesn't interpret escape characters.