Auto unlock and plan next MR once locked MR is released

[syphernl]

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.

---

• [ ] I'd be willing to implement this feature (contributing guide)

Describe the user story

We use Renovate to keep our dependencies up-to-date. As a result we frequently have multiple MR's opened at the same time. Atlantis starts the plan phase for the first opened MR but all subsequent MR's are commented on that the original MR is locked.

Once you have merged the initial MR you need to manually execute atlantis plan for all MR's. This is not practical as it requires manual intervention and costs time.

Describe the solution you'd like

Since Atlantis already knows when an MR is merged (it then automatically releases the plans and locks) it would be nice if it could automatically proceed with the next MR on its own. Once that one has been merged, proceed to the next one until there are none left.

Describe the drawbacks of your solution

I don't see any drawbacks in Atlantis doing (more or less) what now needs to be done manually.

Describe alternatives you've considered

Not using locks, but this is not a preferred method.

[nitrocode]

What if there were

• 3 MRs that were competing for the same directory/project
• the first got the lock
• the second and third were blocked by the first
• the first merged

Then

• Which (second or third) should get autounlocked (and subsequently autoplanned)? By lock date so FIFO? Or random?
• If auto plan is wanted, the code in the second and third are out of date, should they be automerged (or auto rebased) with the default branch?

I think a subsequent autoplan would be difficult to configure but id like an auto unlock using the FIFO approach.

[magmax]

this would be a really nice improvement!

IMHO, autoplan contestants should be just those MR with no additional locks, and I'd vote to sort them, if possible, by:

• MRs with less projects first.
• FIFO in case of same number of projects.

My 2 cents.