dependabot[bot] opened a new pull request, #9513:
URL: https://github.com/apache/camel-quarkus/pull/9513

   Bumps 
[io.quarkiverse.amazonservices:quarkus-amazon-services-bom](https://github.com/quarkiverse/quarkus-amazon-services)
 from 4.0.0.Beta3 to 4.0.0.Beta5.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/quarkiverse/quarkus-amazon-services/releases";>io.quarkiverse.amazonservices:quarkus-amazon-services-bom's
 releases</a>.</em></p>
   <blockquote>
   <h2>4.0.0.Beta5</h2>
   <h2>New features</h2>
   <ul>
   <li>
   <p><strong>Configurable S3 multipart transfers:</strong> standard 
asynchronous S3 clients can now enable multipart support through configuration, 
without a custom producer. This also applies to transfers performed through S3 
Transfer Manager.</p>
   <pre lang="properties"><code>quarkus.s3.multipart.enabled=true
   quarkus.s3.multipart.threshold-in-bytes=100000000
   quarkus.s3.multipart.minimum-part-size-in-bytes=8M
   </code></pre>
   </li>
   <li>
   <p><strong>Extended named-client support:</strong></p>
   <ul>
   <li>S3 service settings and native CRT settings can be overridden per named 
client, with per-property fallback to the default client.</li>
   <li>S3 Transfer Manager supports named standard and native CRT clients.</li>
   <li>DynamoDB endpoint discovery can be configured per named client.</li>
   <li>DynamoDB enhanced clients support per-name extension lists.</li>
   </ul>
   </li>
   <li>
   <p><strong>More flexible AWS configuration sources:</strong> SSM, Secrets 
Manager and AppConfig Data support named resource selections, explicit 
prefixes, document formats and configurable source ordinals. Secrets Manager 
also supports optional polling and batch retrieval.</p>
   </li>
   <li>
   <p><strong>Runtime Secrets Manager and SSM expressions:</strong> read 
individual remote values or JSON fields without enabling a ConfigSource.</p>
   <pre lang="properties"><code>myapp.api-key=${ssm::/myapp/prod/api-key}
   myapp.database.password=${sm::prod/database#/password}
   </code></pre>
   <p>Expressions are resolved lazily at runtime, with successful reads cached 
for five minutes by default.</p>
   </li>
   <li>
   <p><strong>Stored database credentials:</strong> new 
<code>secretsmanager-credentials-provider</code> and 
<code>ssm-credentials-provider</code> integrations retrieve usernames and 
passwords from documents or individual secrets/parameters.</p>
   <p>Credentials are retrieved when the consumer requests them; existing 
database connections are not automatically replaced when credentials rotate.</p>
   </li>
   <li>
   <p><strong>S3 configuration source:</strong> load configuration from 
explicitly selected objects, with optional polling and immutable version 
pins.</p>
   <pre lang="properties"><code>quarkus.s3.config.enabled=true
   quarkus.s3.config.entries.application.bucket=my-config-bucket
   quarkus.s3.config.entries.application.key=config/application.json
   </code></pre>
   </li>
   </ul>
   <h2>Fixes and improvements</h2>
   <ul>
   <li>AWS configuration refreshes publish complete snapshots and retain the 
previous values when a refresh fails, rather than exposing partial updates.</li>
   <li>AppConfig Data improves session recovery and respects server-provided 
polling delays.</li>
   <li>Configuration loading now honors the default service’s configured API 
timeouts and URL Connection timeout/TLS settings.</li>
   <li>AWS configuration diagnostics avoid exposing remote values and sensitive 
exception messages.</li>
   <li>Floci Dev Services automatically selects 
<code>floci/floci:latest-compat</code> when initialization scripts are 
configured. The image includes the AWS CLI, <code>awslocal</code> and boto3. 
Explicit image settings still take precedence.</li>
   <li>Corrected the common runtime SPI extension metadata resource 
location.</li>
   </ul>
   <h2>Notes</h2>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/quarkiverse/quarkus-amazon-services/commit/d4119b2c48fbb8bf47cfd4f51bb06514483a58ce";><code>d4119b2</code></a>
 [maven-release-plugin] prepare release 4.0.0.Beta5</li>
   <li><a 
href="https://github.com/quarkiverse/quarkus-amazon-services/commit/d4df1f21f720e2948cbac4651eb2ed4b52a10a78";><code>d4df1f2</code></a>
 Update the latest release version 4.0.0.Beta5 in documentation</li>
   <li><a 
href="https://github.com/quarkiverse/quarkus-amazon-services/commit/2207c564b239ca18b0e51f534167ab2e66fba5c3";><code>2207c56</code></a>
 chore: release 4.0.0.Beta5</li>
   <li><a 
href="https://github.com/quarkiverse/quarkus-amazon-services/commit/cd1696aed10527643f5d6c0baa9ca1dd1d534253";><code>cd1696a</code></a>
 fix(devservices): select Floci compat image for init scripts</li>
   <li><a 
href="https://github.com/quarkiverse/quarkus-amazon-services/commit/135a9353ea4029becb347b686bc947a0f6018ed1";><code>135a935</code></a>
 docs: group service-specific extensions in navigation</li>
   <li><a 
href="https://github.com/quarkiverse/quarkus-amazon-services/commit/3eaa448ed03062f40b90cd48bd7ec4e86b92afd3";><code>3eaa448</code></a>
 docs: complete Amazon Services 4 migration guide</li>
   <li><a 
href="https://github.com/quarkiverse/quarkus-amazon-services/commit/7851335195b0f6bd6aade98439de2dd961bd0614";><code>7851335</code></a>
 docs: add AWS configuration migration guidance</li>
   <li><a 
href="https://github.com/quarkiverse/quarkus-amazon-services/commit/707caa42c3e41a7b41aa6bf372ab5c50945dc83a";><code>707caa4</code></a>
 feat(s3): load configuration from explicit versioned objects</li>
   <li><a 
href="https://github.com/quarkiverse/quarkus-amazon-services/commit/3e0607a9271ec07a2bccaa8de719a922dbb2a9f1";><code>3e0607a</code></a>
 feat(credentials): supply stored Secrets Manager and SSM credentials</li>
   <li><a 
href="https://github.com/quarkiverse/quarkus-amazon-services/commit/dace2f5a441521e832f5134d414806c3b49de87b";><code>dace2f5</code></a>
 feat(config): resolve runtime Secrets Manager and SSM expressions</li>
   <li>Additional commits viewable in <a 
href="https://github.com/quarkiverse/quarkus-amazon-services/compare/4.0.0.Beta3...4.0.0.Beta5";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=io.quarkiverse.amazonservices:quarkus-amazon-services-bom&package-manager=maven&previous-version=4.0.0.Beta3&new-version=4.0.0.Beta5)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
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]

Reply via email to