Feature Request: use arbitrary hcl files for Atlantis project generation about terragrunt-atlantis-config HOT 4 CLOSED

Yes, pretty much. Right now we are using a nodejs output filter from some guy on github ;-) I guess making changes for run-all workflows in terragrunt_light.js are comparably small. That said I'ld rather have a safe plan/apply workflow without much hassle, than a pretty output.

from terragrunt-atlantis-config.

This is certainly interesting. I also run terragrunt-atlantis-config in a fairly large repo (600 terragrunt modules or so) and don't love the UX of having all of those modules display, but I always found the output of run-all plan to be difficult to parse.

But maybe that's gotten better, as tbh I haven't kept up with the -all commands for quite a few terragrunt versions.

So I just want to make sure I understand your ideal flow here: would it just be the run-all plan output that appears when running atlantis plan -p account_env_region_product?

from terragrunt-atlantis-config.

That's very fair! How are you thinking you'd mark a directory as the root of a project?

from terragrunt-atlantis-config.

I would imagine a parameter like "--project-tgconfig-files=product.hcl,env.hcl" and a separate parameter like "--create-child-projects" (default true) to optionally turn off the creation of terragrunt child module projects.
Edit: maybe "--create-child-projects=false" should only ignore terragrunt childs below project-tgconfig-files? Not every Terragrunt child might be tied to a product or environment.

from terragrunt-atlantis-config.