fix: Enforce explicitly setting SHA in API requests #5146
+4
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
what
I propose adding the Commit SHA as a required field on API requests.
why
When running API Requests, we are currently only requiring the following fields:
However, this is not sufficient information as many operations rely on knowing the exact commit we are working on and not just the Ref, which is a moving target.
Furthermore, it's more reliable to explicitly state the SHA you want to perform actions on, otherwise you could get unexpected results as the pipeline you are currently working with locally might be pointing to a different version of the Ref than the one that Atlantis fetches.
tests
I would like guidance on how to appropriately testing this change as I'm fairly unfamiliar with the Atlantis codebase.
references
closes #5143