Added custom ENV in resource composer_project #54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pbanderas
force-pushed
the
composer-custom-env
branch
from
08e92a1 to
e9af6c5
Compare
Resource now receives a new attribute env, in order to specify additional shell environment variables
pbanderas
force-pushed
the
composer-custom-env
branch
from
e9af6c5 to
5cbd114
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The shell commands for composer only set the COMPOSER_HOME env variable, and there is no way to specify others.
In my case, I needed it to set GIT_SSH env (so it could clone a private package from a private repo) but can be used to set other variables such as $HOME or $USER if necessary (Chef execute resource used inside composer_project does not change these couple, regardless the user/group attributes)