feat(iceberg-catalog-rest): expose invalidate_token, regenerate_token APIs #1465
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
cmcarthur
force-pushed
the
cmcarthur/invalidate-token-apis
branch
from
d98906a to
3708c46
Compare
Xuanwo
approved these changes
Jun 25, 2025
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.
Which issue does this PR close?
What changes are included in this PR?
Per discussion here: #437 (comment)
This branch exposes two public methods on the rest catalog for managing tokens:
invalidate_tokenandregenerate_token.invalidate_token: takes the token lock and sets the token toNone, forcing re-auth on the next requestregenerate_token: calls the oauth endpoint to generate a new token. if successful, takes the token lock and writes the new token.Are these changes tested?
Yes -- I've added new unit tests to cover both methods.