wgtmac commented on PR #1387:
URL: https://github.com/apache/polaris/pull/1387#issuecomment-2812018853
I am working on credentials vending while integrating our lakehouse with
Polaris catalog and happened to see this possible typo, am I correct?
At the same time, I have a question about the keys for storage credentials.
The spec has the following description for `LoadTableResult`.
```
## AWS Configurations
The following configurations should be respected when working with
tables stored in AWS S3
- `client.region`: region to configure client for making requests
to AWS
- `s3.access-key-id`: id for credentials that provide access to the
data in S3
- `s3.secret-access-key`: secret for credentials that provide
access to data in S3
- `s3.session-token`: if present, this value should be used for as
the session token
- `s3.remote-signing-enabled`: if `true` remote signing should be
performed as described in the `s3-signer-open-api.yaml` specification
## Storage Credentials
Credentials for ADLS / GCS / S3 / ... are provided through the
`storage-credentials` field.
Clients must first check whether the respective credentials exist in
the `storage-credentials` field before checking the `config` for credentials.
```
Does it mean that different catalog vendors are free to use whatever keys
for different storage in the `storage-credentials`? Is there any chance to
standardize them?
--
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]
