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

Upgrade to quarkus-amazon-services 2.4.2 and migrate to @ConfigMapping #160

Merged
merged 2 commits into from
Aug 1, 2023

Conversation

yrodiere
Copy link
Collaborator

@yrodiere yrodiere commented Aug 1, 2023

Necessary to catch up with quarkus-amazon-services, which migrated to @ConfigMapping. The build just fails otherwise because we'd be mixing @ConfigMapping from quarkus-amazon-servivces with old-style configuration.

The generated documentation for configuration properties is not great at the moment (it only mentions configuration for named PUs/backends) because Quarkus 3.2 doesn't include quarkusio/quarkus#34514 , but it's simpler that way. Let's wait for a backport in 3.2 or for 3.3 to get correct documentation.

dependabot bot and others added 2 commits August 1, 2023 09:45
Bumps `quarkus-amazon-services.version` from 2.4.0 to 2.4.2.

Updates `io.quarkiverse.amazonservices:quarkus-amazon-services-bom` from 2.4.0 to 2.4.2
- [Release notes](https://github.com/quarkiverse/quarkus-amazon-services/releases)
- [Commits](quarkiverse/quarkus-amazon-services@2.4.0...2.4.2)

Updates `io.quarkiverse.amazonservices:quarkus-amazon-common` from 2.4.0 to 2.4.2

---
updated-dependencies:
- dependency-name: io.quarkiverse.amazonservices:quarkus-amazon-services-bom
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: io.quarkiverse.amazonservices:quarkus-amazon-common
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Necessary to catch up with quarkus-amazon-services

See quarkiverse/quarkus-amazon-services#836
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant