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.

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

Some environment variables are set too early for options/switches to have an effect #620

Closed
ferventcoder opened this issue Feb 10, 2016 · 0 comments

Comments

@ferventcoder
Copy link
Member

No description provided.

@ferventcoder ferventcoder self-assigned this Feb 10, 2016
@ferventcoder ferventcoder added this to the 0.9.10 milestone Feb 10, 2016
@ferventcoder ferventcoder changed the title Verify environment variables are not set too early so that overrides from configuration are available Some environment variables are set too early for options/switches to have an effect Jun 5, 2016
ferventcoder added a commit that referenced this issue Jun 5, 2016
After all options and configuration have been set, then set the
environment variables.
ferventcoder added a commit that referenced this issue Jun 5, 2016
Provide a way to update pro/business environment values that are set.
Pro/business was already doing this out of bound, but this allows for
more consistency in controlling when those values are set.
ferventcoder added a commit that referenced this issue Jun 5, 2016
* stable:
  (GH-439) Refresh Environment Before Package Scripts
  (GH-439) Update Environment Variables
  (GH-439) Environment adapter GetEnvironmentVariables
  (maint) formatting
  (maint) rename Environment Path Separator
  (GH-620) Set pro/business environment
  (GH-620) Set environment variables after options
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants