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

Preserve environment when calling scripts #25

Closed
paullexen opened this issue Sep 12, 2018 · 1 comment · Fixed by #26
Closed

Preserve environment when calling scripts #25

paullexen opened this issue Sep 12, 2018 · 1 comment · Fixed by #26

Comments

@paullexen
Copy link

Currently the runScript function creates a fresh environment with only the TAG and REPO_NAME variables. It would be nice if it would instead use the current process.env and just add those extra variables to it. That way useful variables such as PATH will be accessible to deployment scripts.
@maccyber
Copy link
Owner

maccyber commented Oct 3, 2018

Sorry for the late reply.
It sounds like a good idea, do you have the opportunity to send a pull request?

@paullexen paullexen mentioned this issue Oct 3, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Preserve environment variables when calling scripts
2 participants
@maccyber @paullexen