docs: sync the substitutions chapter and the stacker file article #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
Signed-off-by: mbshields <mshields@alum.mit.edu>
|
|
||
| In the yaml directives, stacker allows variable substitions of several forms. For example, these three substition statements: | ||
|
|
||
| $ONE ${{TWO}} ${{THREE:3}} |
There was a problem hiding this comment.
Whoops, we missed this part when I updated the stacker.yaml reference - we do not support $ONE anymore, it is OK to have that in the run section but it'll be interpreted as a shell variable by the shell running in the run section.
It will not be treated as a substitution, and if you run stacker build --substitute ONE=1 on this example you will get an error.
please see project-stacker/stacker#612 for my rewritten version of this in the source
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 substitution sections of these two files are now updated and in sync with each other. There is redundancy, but these two documents are likely to be arrived at from different circumstances -- one is part of the user guide and the other is a reference. This should address Issue #51