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

Enable terragrunt run-all apply without using Atlantis project flag #5224

Open
1 task done
talesrc opened this issue Jan 8, 2025 · 0 comments
Open
1 task done

Enable terragrunt run-all apply without using Atlantis project flag #5224

talesrc opened this issue Jan 8, 2025 · 0 comments
Labels
feature New functionality/enhancement

Comments

@talesrc
Copy link

talesrc commented Jan 8, 2025

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Describe the user story

As a developer, I'd like to run terragrunt run-all apply without specifying the Atlantis project flag across multiple Atlantis projects. Each of my projects would have multiple modules, and as a result, the plan would be saved in the .terragrunt-cache folder of each module, not having the $PLANFILE created.

Currently, I've worked around this use-case by creating an empty $PLANFILE to trigger the project apply.

Atlantis version: v0.32.0

Describe the solution you'd like

The solution could be to set an attribute which would dynamic find the plans with a given name, something like running a find -type f -name "{plan-file-name}", which has the capability to find the files only within the Atlantis project folder.

Describe the drawbacks of your solution

As each Atlantis project is going to have zero or more plans, the Conftest usage would need to also be refactored to support multiple plans.

Describe alternatives you've considered

  • Refactoring our IaC structure to create an individual Atlantis project for each module wouldn't be practical, as it would disrupt the relationships between modules and could result in unexpected behavior.

  • Keep using with the workaround, with an empty plan file to trigger the apply, will not work when we start to use Conftest.

@talesrc talesrc added the feature New functionality/enhancement label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality/enhancement
Projects
None yet
Development

No branches or pull requests

1 participant