Change order of parsing so that include is parsed first #898
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.
This is a fix for #814 (comment). Specifically, right now due to the parsing order
get_parent_terragrunt_dir
does not work inlocals
. This breaks usage of locals to refactor out a path calculation that depends on the parent dir, such as getting a defaultempty.yml
file in the workaround for merging in optional variables from the directory hierarchy.Note that this is a backwards incompatible change, where you can no longer reference
locals
ininclude
. However, this is probably a worthy tradeoff where we are trading the not so useful function of referencinglocals
ininclude
blocks (which will in 80% of use cases befind_in_parent_folders()
) with the ability to useinclude
dependent functions in the parentlocals
.