You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, while configuring plugins on AWS service clients only service client configuration is passed onto the plugin. However, having access to the client-level context params available as part of service client configuration will simplify and expand the use cases of plugins.
Use Case
As an example, Our team is implementing a plugin that can be attached to the AWS S3 Clients. S3 Clients today support cross-region setting that is only available as part of client-context params. We want our plugin to be able to support cross-region access as well. Since, the plugin does not have access to the client-context params, our approach currently is to have the customers turn-on cross-region setting on the plugin along with the setting on the S3Client. This approach might cause unexpected errors if the customers forgets to turn-on the setting on one of the S3Client or the plugin but not on the other. However, if the plugin has access to the client-context params, we can drop the cross-region setting on the plugin by referencing the configuration on the S3 Client thereby reducing unexpected behaviors.
Proposed Solution
No response
Other Information
No response
Acknowledgements
I may be able to implement this feature request
This feature might incur a breaking change
AWS Java SDK version used
2.22.3
JDK version used
1.8
Operating System and version
MacOS Sonoma 14.2.1
The text was updated successfully, but these errors were encountered:
Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the feature
Currently, while configuring plugins on AWS service clients only service client configuration is passed onto the plugin. However, having access to the client-level context params available as part of service client configuration will simplify and expand the use cases of plugins.
Use Case
As an example, Our team is implementing a plugin that can be attached to the AWS S3 Clients. S3 Clients today support cross-region setting that is only available as part of client-context params. We want our plugin to be able to support cross-region access as well. Since, the plugin does not have access to the client-context params, our approach currently is to have the customers turn-on cross-region setting on the plugin along with the setting on the S3Client. This approach might cause unexpected errors if the customers forgets to turn-on the setting on one of the S3Client or the plugin but not on the other. However, if the plugin has access to the client-context params, we can drop the cross-region setting on the plugin by referencing the configuration on the S3 Client thereby reducing unexpected behaviors.
Proposed Solution
No response
Other Information
No response
Acknowledgements
AWS Java SDK version used
2.22.3
JDK version used
1.8
Operating System and version
MacOS Sonoma 14.2.1
The text was updated successfully, but these errors were encountered: