CASMTRIAGE-7355: Update tapms to fix tenant deletion #3694
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary and Scope
Fixes an issue where deletion events were triggering the mutation web hook, which does not receive the old object information and fails. Now only validation web hooks will trigger the delete events.
The update also includes global tenant hooks which had not been merged to the main branch.
Issues and Related PRs
Testing
Tested on:
Test description:
Validated tenant creation, update and deletion. Previously tenants could not be deleted.
Risks and Mitigations
None
Pull Request Checklist