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.
Overview of the Issue
We have noticed that there are instances where atlantis goes ahead with merging a PR in the event of an apply error which seems to be a bug in the system. Ideally, when the atlantis apply results in an error, it should not merge the PR.
Screenshot :
Reproduction Steps
Raised the PR
Ran atlantis plan which showed the expected changes.
Ran atlantis apply . This resulted in the Apply Failed error stating "Pull request must be mergeable before running apply."
It should have stopped at this stage on failure, however, atlantis went ahead and merged the PR.
Environment details
Atlantis version: v0.26.0
Atlantis flags:
Atlantis server-side config file: We use upstream server-side config
Community Note
Overview of the Issue
We have noticed that there are instances where atlantis goes ahead with merging a PR in the event of an apply error which seems to be a bug in the system. Ideally, when the atlantis apply results in an error, it should not merge the PR.
Screenshot :
Reproduction Steps
It should have stopped at this stage on failure, however, atlantis went ahead and merged the PR.
Environment details
Atlantis server-side config file: We use upstream server-side config
Repo
atlantis.yaml
file:The text was updated successfully, but these errors were encountered: