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

Remove need for repetitive boilerplate terragrunt.hcl #3077

Open
DevopsMercenary opened this issue Apr 19, 2024 · 0 comments
Open

Remove need for repetitive boilerplate terragrunt.hcl #3077

DevopsMercenary opened this issue Apr 19, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@DevopsMercenary
Copy link

Describe the solution you'd like

I've been using Terragrunt for a while and it's really great and helpful.

But, I get tired of having to put the standard include to tell them to include the configuration from the root in every child.

repetitive "terragrunt.hcl"

include "root" {
  path = find_in_parent_folders()
}

There are now hundreds of these three line duplicate terragrunt.hcl files in my project. Repeating, adding this file over and over doesn't seem very DRY to me.

I would like to have added an ENVIRONMENT_VARIABLE flag or command line parameter, like --includerootpathfindinparentfolders, that when enabled or provided, Terragrunt would automatically perform the behavior as if the terragrunt.hcl file existed. The assumption would be that Terragrunt would start searching from the directory where Terragrunt was executed from.

Describe alternatives you've considered

I have not been able to think of any alternatives, nor find any existing option in the Terragrunt documentation

@DevopsMercenary DevopsMercenary added the enhancement New feature or request label Apr 19, 2024
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

No branches or pull requests

1 participant