Hi guys, how are you doing? We’re using terragrunt...
# atlantis-community
l
Hi guys, how are you doing? We’re using terragrunt-atlantis and we’re facing an issue. I have a directory with this structure: /aws/aws-account/region/db-egine/db-type/db-name/terragrunt.hcl /aws/aws-account/region/db-egine/db-type/db-name/initial-setup/terragrunt.hcl When I modify the database’s terragrunt.hcl it’s trigging the autoplan for the initial-setup path, how can I prevent this behavior? I only want to run my autoplan on the database’s manifest file. Thanks in advance!
p
you need to modify the autoplan behaviour and use you own file list type
Copy code
autoplan:
    when_modified: ["*.tf", "../modules/**/*.tf", ".terraform.lock.hcl"]
    enabled: true
g
I’m curious, would you mind sharing why you have an initial setup workflow? Terraform is usually used to ensure all the infrastructure is up to date and those two are related 👀 You might also want to look at https://github.com/transcend-io/terragrunt-atlantis-config if you don’t want to manually manage your path inclusions.