Add check for 403 during rollback to prevent deletion spam #97
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.
Overview
This change addresses an issue where the client will continue to attempt a deletion rollback when the create fails with a 403. A check was implemented in the rollback behavior to check for a 403 response. When a 403 is observed, the WAL is removed to prevent repeated attempts at rollback of a non-existent entity.
Test Plan
vault secrets enable gcp
google.iam.admin.v1.IAM.DeleteServiceAccount
call comes throughContributor Checklist
[x] Add output for any tests not ran in CI to the PR description (eg, acceptance tests)