GitLab pipeline status does not change to success if re-plan is being done

[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.

---

Overview of the Issue

Atlantis did a plan for 12 directories/workspaces. One of them failed (because of a temporary issue on the host running Atlantis). As a result the job is marked as failed.
Afterwards I issued an atlantis plan -d .... -w ..... which finished successfully.

The GitLab pipeline status however remained "failed" .

Reproduction Steps

• Run a plan task of > 2 modules of which one fails (e.g. DNS issue, typo etc)
• Atlantis reports "Plan Error"
• Fix the faulty module
• Issue atlantis plan -d ..... -w ...... in GitLab MR comments
• Atlantis reports "No changes"
• See that the status of the failing job is still "failed" instead of "success", and when clicked leads to the previous (failed) run.

[joaoluchetti]

+1

[brontolinux]

Greetings! I have just commented in #4950 to report that 0.30.0 has the same problem that's described there and we had to revert to 0.28.5.