Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuring AWS SDK Retry Policies via application.properties #1501

Open
Shanzeee opened this issue Nov 22, 2024 · 1 comment
Open

Configuring AWS SDK Retry Policies via application.properties #1501

Shanzeee opened this issue Nov 22, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@Shanzeee
Copy link

Hi everyone,

I’ve been working on configuring the retry behavior for AWS SDK clients in Quarkus applications, and I noticed there’s no built-in way to define retry policies (e.g., RetryMode or maximum retries) via the application.properties file.

Currently, configuring AWS SDK retry policies requires manually creating a custom bean with ClientOverrideConfiguration.

Example for DynamoDbAsyncClient:

DynamoDbAsyncClient.builder()
    .overrideConfiguration(
        ClientOverrideConfiguration.builder()
            .retryPolicy(RetryMode.STANDARD)
            .build()
    )
    .build()

This approach works but feels inconsistent with Quarkus's configuration-driven approach.

Questions:

  • Is there an easier way to configure retry policies that I might have missed?
  • Are there plans to support properties like this in the future?

Thanks in advance for your help!

@scrocquesel
Copy link
Member

scrocquesel commented Nov 22, 2024

Hi,

Does something very simple like this would be enough.

quarkus.dynamodb.advanced.retry-strategy.retry-mode=STANDARD # one of RetryMode enum
quarkus.dynamodb.advanced.retry-strategy.max-attempts=3

@scrocquesel scrocquesel added the enhancement New feature or request label Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants