[OpenAPI Modification] Change revokeGrantFromCatalogRole successful status to 204 (No Content) #2616
Conversation
This file contains hidden or 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
…tatus to 204 (No Content)
Contributor
|
If I'm not mistaken this change stems from https://lists.apache.org/thread/wbmvf8s0sdwhfn8p91pwqsxolxd2btj4 I am personally not convinced that changing the response code is worth the possible ripple effects on the client side. I believe it might be worth a dedicated |
Contributor
Author
|
Issue for this here: #2657 |
Contributor
|
More specific discussion thread: https://lists.apache.org/thread/bhd1srzks0pz0odoqmm87gfyj2yz2k41 |
|
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
github-project-automation
bot
moved this from PRs In Progress
to Done
in Basic Kanban Board
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As per ML thread. This should cause a major version upgrade - as such, do not merge until Polaris 2.x.x is ready.