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

source environment file in all chef extension files #134

Conversation

dheerajd-msys
Copy link
Contributor

Currently some environment variables are not getting sources if they are set in .bashrc or other places, as the extension script's hasbang uses sh
So sourcing /etc/environment file in the extension scripts

In-Progress

@dheerajd-msys dheerajd-msys force-pushed the dh/read_environment_variable branch from dfeda9f to 138bb05 Compare May 18, 2016 07:03
@Knappek
Copy link

Knappek commented May 20, 2016

Hi, does somebody takes care about solving these conflicts?

@NimishaS
Copy link

Hello @Knappek , we are planning to provide a general solution for this kind of problem. So we'll be adding a feature to allow user to pass environment variables in the extension itself through extension's settings parameter. The extension will source it. There is a discussion in progress for this feature.
So this PR will be closed soon.

@Knappek
Copy link

Knappek commented May 20, 2016

@NimishaS, ok that is a pretty cool solution :). Thanks for the update!

@NimishaS
Copy link

Fixed in #141

@NimishaS NimishaS closed this Sep 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants