sdaberdaku commented on issue #17860: URL: https://github.com/apache/iceberg/issues/17860#issuecomment-5457365337
Update: after review on #17862 the fix is being narrowed. Instead of deriving the S3A assume-role settings from `client.assume-role.arn`, the listing will honour the per-catalog `spark.sql.catalog.<name>.hadoop.*` overrides, which today are accepted but ignored on this path. For the setup above that means: ``` spark.sql.catalog.tenant.hadoop.fs.s3a.aws.credentials.provider org.apache.hadoop.fs.s3a.auth.AssumedRoleCredentialProvider spark.sql.catalog.tenant.hadoop.fs.s3a.assumed.role.arn arn:aws:iam::111122223333:role/lakehouse-access spark.sql.catalog.tenant.hadoop.fs.s3a.assumed.role.credentials.provider com.amazonaws.auth.WebIdentityTokenCredentialsProvider ``` Per catalog, no bucket scoping. Deriving the role from the catalog's own properties may come as a follow-up. -- 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]
