add packer variable files option #694
Closed
Conversation
This file contains 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
|
Looks fine to me; if you resolve the conflict and rename this |
|
This will be resolved by #1079 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue #, if available:
Description of changes:
Add packer variable file environment variables for users to specify the custom variable files for packer. Users now can only set variables dynamically by setting
PACKER_VARIABLES. If users want to modify few more variables which are not listed intPACKER_VARIABLES, then it would be helpful for them to define variables in json file and specify the file name toPACKER_VAR_FILEBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.