This repository has been archived by the owner on Mar 3, 2023. It is now read-only.
Use password stored in an environmental variable #5
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've had a difficult time integrating this module into some continuous delivery pipelines like PM2 because for some reason (I really don't know why) piping a password using echo (
echo 'my_pass' | npm run encrypt
) doesn't work in the isolated environments set up to build and deploy code.To get around this, I've added support for a single flag
--PW
to which you pass the name of an environmental variable set to a desired password.Example use in
package.json
:encrypt: encrypt config.json config.json.cast5 --PW=ENV_VAR
This by-passes manual password entry from stdin and instead uses the value found at the --PW environmental variable, if it exits. If the environmental variable is not set, the command exits with exit status 1.