with terragrunt-alantis-config, do i still need to commit the alantis.yaml to github ?

[ishallbethat]

I don't know how to make the atlantis.yaml automatically generated every time i create a pull request, and atlantis can pick up this auto generated file then do terragrunt plan or apply.

I think this would be best if atlantis.yaml can be auto generated and i don't need to keep track of this file in github repo.

[michaelfarrell76]

the plan for this is atlantis is adding a feature to allow for pre-workflow custom hooks

see the issue
and the open pr

[michaelfarrell76]

for now would recommend committing the atlantis.yaml until that is merged

[ishallbethat]

I'm looking at "terragrunt-atlantis-config using github action to validate atlantis.yaml" . I'm not sure it's a way to achieve what i need. @michaelfarrell76

[angeloskaltsikis]

@IamGabrielWu You can follow the method described in this medium post till the PR of having pre-workflow custom hooks is merged.

I would advise against committing as you will have each user run the current project
cc. @michaelfarrell76

[dmattia]

I'm going to close this, but feel free to open if you have any other questions.

To summarize:

• you can keep committing atlantis.yaml to github
• @angeloskaltsikis has a very nice solution you can migrate to now to not need to commit
• fairly soon, atlantis should support hooks that are another option for not needing to commit

[dmattia]

runatlantis/atlantis#1255 has been released in Atlantis v0.16.0, allowing us to run terragrunt-atlantis-config on the Atlantis server side of things.

I'll be updating the documentation of this repo soon with how to use the new features 😄

[tsunamishaun]

@angeloskaltsikis the post wasn't entirely clear on how to setup the post-clone git hook, I ended up putting the core.hooksPath in /etc/gitconfig with /home/atlantis/hooks as the path. Though I am using the new pre-workflow feature of atlantis it doesn't consistently run for subsequent workspaces, making my atlantis.yaml not clone into each workspace directory. I am using both methods now and things appear stable, would love to keep the conversation going and see what you come up with @dmattia.

My use case is for multi account and by passing in account name I'm able to generate the config just for the instance of atlantis set for the account. This line is in my root terragrunt.hcl (hopefully it helps someone else):

locals {
  atlantis_skip = get_env("ATLANTIS_ENABLED_ACCOUNTS", "") == local.account_name ? false : true
}

It does mean that bad configs will break everything and that there is no way to ignore a directory (per the way I am parsing the environment variable, suggestions welcome!).

[kitos9112]

Many thanks @tsunamishaun for sharing the above code snippet. It has just solved the first impediment I was facing with this fantastic tool to generate the atlantis.yaml - Although, I slightly modified the Terraform built-in function as I didn't bother about hardcoding the name of my AWS workload in the top-level terragrunt.hcl:

locals {
  (...)
  atlantis_skip = contains(["dev"], local.aws_account_workload) ? false : true
}

At the moment, we only let Atlantis run in our AWS development account so we can take careful decisions about moving code into other more sensitive environments by leveraging a dedicated GitLab runner.

I even think it should be clearly indicated in the README.md of this project given the fact it also works despite utilising the CLI flag --ignore-parent-terragrunt:

How to limit the automatic generation of an atlantis.yaml configuration for a well-known Terragrunt directory-driven layout:

account
 └ _global
 └ region
    └ _global
    └ environment
       └ resource