follow symlinks for path_relative_to_include #1550
Open
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.
Closes #543
My use case involves wanting to prefix terragrunt dirs with numbers to make the stage order obvious, generate state keys based on path to ensure uniqueness, and use a fair number of
terraform_remote_state
objects.Reordering or inserting stages is a time-consuming process involving moving many different state files, adjusting
terraform_remote_state
objects, and renaming folders.Also,
cd
ing isn't as frictionless as it could be; with the extra often 0-padded prefixes.Creating numbered symlinks to the terragrunt dirs (but having terragrunt ignore those symlinks) would be an ideal solution.
Things to consider:
path_relative_to_include
should take a boolean argument if possible; defaulting to the old behavior but allowing the use of this behavior.path_relative_from_include
too?filepath.Clean
on the path too?