-
Notifications
You must be signed in to change notification settings - Fork 93
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
Parent Terragrunt is included as dependency #235
Comments
After some digging I found out that this behavour was introduced in It mentions the changes but doesn't reflect them in documentation:
I'll keep this issue open in case I'll find the time to work on the |
same issue here on latest 1.15.0 file below is the parent nonprod/terragrunt.hcl which i want to exclude from plans.
file below is the child in
sample from atlantis.yaml created by version 1.15:
sample from atlantis.yaml created by version 1.13 with same command
not sure if this comment belongs here, or in #217 so i've posted in both. sorry! |
Was just about to open an issue, I am seeing the same problem. It would be nice to have a way to ignore the extra top-level |
Has anyone been able to find a work around for this? |
I use this hacky workaround in Atlantis config. Since my directory structure is consistent, I just remove the root file from all projects each time
|
@enarmontas I was thinking about doing something similar. Glad to hear it wasn't as crazy as I thought! Thanks for the reply, I will give something like that a try. |
I think there might be a misunderstanding here on the feature supported by So if you want to avoid triggering a plan/apply for all your projects each time there's a change in the parent terragrunt config and you are using include blocks, there's for now no other way than using a sed as suggested by @enarmontas . |
Here is my parent
terragrunt.hcl
:Here is my child
terragrunt.hcl
Here is the command I run:
And here is the resulting Atlantis config:
Why does it include the parent config
../../../../../terragrunt.hcl
? Is there a bug or I am doing something wrong?I am using the latest version.
The text was updated successfully, but these errors were encountered: