You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The env/dev symlink is just a convenience for manually navigating the directory structure. The terragrunt config specifies a remote state path using path_relative_to_include(). This evaluates differently depending on whether you've navigated to the directory directly or via the symlink. Is this desirable behavior, or should the symlink be expanded?
The text was updated successfully, but these errors were encountered:
Ah, I don't think we tested those functions with symlinks. My guess is we'd want to expand those paths fully so they are "canonical" paths and always the same. PR for that is welcome.
We have the following kind of setup:
The
env/dev
symlink is just a convenience for manually navigating the directory structure. The terragrunt config specifies a remote state path usingpath_relative_to_include()
. This evaluates differently depending on whether you've navigated to the directory directly or via the symlink. Is this desirable behavior, or should the symlink be expanded?The text was updated successfully, but these errors were encountered: