Add ability to pass arbitrary environment variables via envionment
attribute in delivery_test_kitchen block
#39
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.
Hello,
This PR is in reference to #38 .
Basically, this is the monkey-patch that I'm using to enable to me to pass Environment variables to test kitchen runs/our
.kitchen.yml
. The framework was already there, and everywhere it seems like it was assumed that env vars might be passed in, but the facilities to actually pass env vars was not there.This PR enables the ability to pass environment settings a la:
If I'm being totally honest, this PR exists mostly because it reduces the monkey patching I have to do... but also if I'm trying to pass env vars, who else has a similar use case?
Thanks,