You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
Community Note
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.
The text was updated successfully, but these errors were encountered: