This message was deleted.

I have 2 dir, one is set to

execution_order_group: 1

& the other

execution_order_group: 2

. When I run

atlantis plan

, I’m seeing both plans get generated, with one failing (since it has a hard dependency from another state file).

In this case you should apply first project locally. Now, Atlantis plans all dependent projects. I’m gonna make Atlantis more suitable for terragrunt and fix this case

that defeats the purpose of the execution order flag on atlantis though. I can’t and don’t want to expect end-users to run local plans.

it controls order of applying/planning. This parameter guarantees that project with smaller group planning/applying first. Without it, we can't even apply two dependent projects, because order of projects in Atlantis doesn't match with terragrunt's order. Atlantis shows plans in all changed projects. But in your case, the second one should be planned after applying of first project. Hmm, you can split PR by two. First is changes in dir 1, and second in dir 2

Yes I want to avoid splitting PR for simpler UX. But I get what the flag is used for now. Ty.