Add deployment environment variables #223
Assignees
Labels
Comments
lholmquist
added a commit
to lholmquist/nodeshift
that referenced
this issue
May 21, 2018
This will allow users to pass in environment variables that should be added to a deployment config. ex: nodeshift --deploy.env NODE_ENV=development If a deployment.yaml in the .nodeshift directory already exists with environment variables, they will be merged together If there are duplicate vars, the ones passed in from the cli/api will take precedence. fixes nodeshift#223
ghost
added
lholmquist
added a commit
to lholmquist/nodeshift
that referenced
this issue
May 22, 2018
This will allow users to pass in environment variables that should be added to a deployment config. ex: nodeshift --deploy.env NODE_ENV=development If a deployment.yaml in the .nodeshift directory already exists with environment variables, they will be merged together If there are duplicate vars, the ones passed in from the cli/api will take precedence. fixes nodeshift#223
lholmquist
added a commit
that referenced
this issue
May 22, 2018
This will allow users to pass in environment variables that should be added to a deployment config. ex: nodeshift --deploy.env NODE_ENV=development If a deployment.yaml in the .nodeshift directory already exists with environment variables, they will be merged together If there are duplicate vars, the ones passed in from the cli/api will take precedence. fixes #223
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If someone wanted to add some environment variables to their deployment config, they would have to create a deploymentConfig.yaml and place it in the
.nodeshiftdirectoryI think we can probably add a cli flag called
--deploy.envthat will allow the user to add 1 or more environment variables.This is sort of the same thing that happens with the
--build.envflag, but for buildConfigsThe text was updated successfully, but these errors were encountered: