cloudtools / cloudtools/stacker
Environment variables should be evaluated after yaml parse
Open
- Dominant language
- Python
- Stars
- 707
- Forks
- 162
- PR merge metrics
- No merged PRs in 30d
Description
When there is a variable in the yaml that isn't defined the stack fails as expected. If I disable that stack, it still fails. If I comment out the line, it still fails. It seems like the variable replacement should be moved until after the yaml parse, or maybe the variable replacement to be taught to ignore disabled and/or commented lines.
stacker-1.0.4
Contributor guide
Assessment
This issue has not been assessed yet.