Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Could we *Optionally* Export the Environment Variables used in CodeShip into an .env file ? #31

Closed
nelsonic opened this issue Apr 1, 2016 · 0 comments
Closed

Could we *Optionally* Export the Environment Variables used in CodeShip into an .env file ? #31

nelsonic opened this issue Apr 1, 2016 · 0 comments
Labels
enhancement help wanted question

Comments

@nelsonic
Copy link
Member

nelsonic commented Apr 1, 2016 •
edited
Loading

as a responsible developer, I don't want to publish my Secret Keys (e.g. AWS Tokens or Endpoint URLs) to GitHub, but given that these keys need to be available for testing/deployment on CodeShip (as environment variables) ... can't we take advantage of this fact?

If we set an option in files-to-deploy we could export the environment variables (process.env)
used on CodeShip as an .env file which we can then load into the Lambda using env2 (or similar .env file loader)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement help wanted question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nelsonic