Added pre-processing to env.sh for things like encryption #142
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
with a custom env.sh sourcing script you can do things like gpg encrypt your env.sh file
Use env_handler.sh as a pre-processor for your env.sh scripts
Closed
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.
Took advantage of the iron-cli dep shell-source feature of custom sourcing wrappers. This way you can decide how to source the env.sh file. The example given is encrypting your env.sh files so creds don't show up in the git repo. Wouldn't be any problem to have different keys for development and production if desired.
Previously scaffolded out config/development/env.sh remains untouched.
Adds scaffolding for bin/env_handler.sh with encrypting example commented out.
Should work on windows (took great care to build paths windows compatible).... tested on OSX....