leekeiabstraction commented on PR #1245: URL: https://github.com/apache/fluss/pull/1245#issuecomment-3590396376
> any ideas how we can achieve this despite the behavior of fs.s3a.assumed.role.credentials.provider? maybe we can set fs.s3a.assumed.role.credentials.provider to a credential provider that uses short-term credentials and remove the long-term credential providers from s3.aws.credentials.provider's default chain (instead of setting it to blank)? I may need to sync to understand the user experience that we want in terms of happy cases as well. But if you intend to support this specific scenario ie user should run into error when they disable token delegation without specifying 's3.aws.credentials.provider', my suggestion is that we should check the configurations and fail-fast by throwing an exception at the configuration stage, rather than passing it on and relying on dependency's behaviour. Also, modifying credentials provider behind the scene might catch user by surprise. -- 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]
