netapp-acheng commented on issue #3440:
URL: https://github.com/apache/polaris/issues/3440#issuecomment-3770899690
I read the change you made today (Jan 19) in pr-3445, you have
- Added KMS options to Polaris CLI.
- Changed from Poetry to UV for Python package management.
- Exclude KMS policies when KMS is not being used for S3.
Looked at ./polaris catalogs create -h, did not see new KMS related option.
These two options were there before pr-3445.
--current-kms-key (Only for AWS S3) The AWS KMS key ARN to be used
for encrypting new S3 data
--allowed-kms-key (Only for AWS S3) AWS KMS key ARN(s) that this
catalog and its clients are allowed to use for reading S3 data (zero or more)
When I created the catalogs, I did not specify any of these kms option.
"roleArn": "arn:aws:iam::123456789101112:role/assumerole",
"allowedKmsKeys": [],
"region": "us-east-1",
"endpoint": "https://sgdemo.example.com/";,
"stsEndpoint": "https://sgdemo.example.com/";,
"stsUnavailable": false,
May be should add --no-kms option for catalogs create CLI.
--
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]
