Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

path_relative_to_include and symlinks #543

Open
jbergknoff-rival opened this issue Aug 14, 2018 · 2 comments · May be fixed by #1550
Open

path_relative_to_include and symlinks #543

jbergknoff-rival opened this issue Aug 14, 2018 · 2 comments · May be fixed by #1550
Labels
enhancement New feature or request

Comments

@jbergknoff-rival
Copy link

We have the following kind of setup:

dev-account/us-west-2/env-dev/terraform.tfvars
env/dev -> dev-account/us-west-2/env-dev

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?

@brikis98 brikis98 added enhancement New feature or request help wanted labels Aug 14, 2018
@brikis98
Copy link
Member

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.

@Patricol Patricol linked a pull request Feb 13, 2021 that will close this issue
@brikis98
Copy link
Member

Note that full symlink support will also depend on #1611.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants