nastra commented on code in PR #15280:
URL: https://github.com/apache/iceberg/pull/15280#discussion_r3086555218
##########
open-api/rest-catalog-open-api.yaml:
##########
@@ -1227,7 +1234,17 @@ paths:
type: string
description: The plan ID that has been used for server-side scan
planning
- $ref: '#/components/parameters/referenced-by'
- description: Load vended credentials for a table from the catalog.
+ - $ref: '#/components/parameters/storage-refresh-token'
Review Comment:
I don't think we actually want to have one refresh token for each individual
storage credential. To me the refresh token is just passing some additional
context around so that the server knows that a client is trying to refresh
credentials within the context of X. So that means we would have a 1:N mapping
between refresh token and one or more storage credentials (after all, the
responses of different endpoint are capable of returning more than one storage
credential for a given table)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
