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.
A clear and concise description of what workflow is meant to be improved.
Pre-workflow hook scripts we run perform some custom inspection of PR state using the Gitlab API and we want to optionally halt atlantis locking and workflows kicking off if a pre-workflow hook returns a non-zero exit code.
Describe the solution you'd like
A clear and concise description of what you want to happen. Consider that atlantis is used
by many people, and your particular use case might not make sense to implement in the core.
Simply allow this:
repos:
- id: xxxpre_workflow_hooks:
- run: /some/script.sh must_succeed: true # defaults to false if omitted
This sort of thing we hope prevents atlantis locking pull requests that we know ahead of time aren't fit for atlantis's attention.
Describe the drawbacks of your solution
must_succeed makes less sense in a post_workflow hook so in the code this distinction must be made clear.
Describe alternatives you've considered
Considered a workflow generator script, but adds a lot of complexity and not as flexible as addint a must_succeed arg to a given pre-workflow hook.
The text was updated successfully, but these errors were encountered:
Community Note
Describe the user story
A clear and concise description of what workflow is meant to be improved.
Pre-workflow hook scripts we run perform some custom inspection of PR state using the Gitlab API and we want to optionally halt atlantis locking and workflows kicking off if a pre-workflow hook returns a non-zero exit code.
Describe the solution you'd like
A clear and concise description of what you want to happen. Consider that atlantis is used
by many people, and your particular use case might not make sense to implement in the core.
Simply allow this:
This sort of thing we hope prevents atlantis locking pull requests that we know ahead of time aren't fit for atlantis's attention.
Describe the drawbacks of your solution
must_succeed
makes less sense in apost_workflow
hook so in the code this distinction must be made clear.Describe alternatives you've considered
Considered a workflow generator script, but adds a lot of complexity and not as flexible as addint a
must_succeed
arg to a given pre-workflow hook.The text was updated successfully, but these errors were encountered: