-
Notifications
You must be signed in to change notification settings - Fork 52
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
Warnings about unrecognized config keys after upgrade to Quarkus 3.18.1 #1564
Comments
The problem can also be seen in the dependabot build for upgrading this repo to Quarkus 3.18.1: |
/cc @radcortez |
I'll have a look |
@steinsag I'm getting a 404 with the reproducer. Maybe it is private? |
@radcortez Sorry, you are right, now the repo is public. But as I said, you can also see it in the dependabot build here in the repo: https://github.com/quarkiverse/quarkus-amazon-services/actions/runs/13047086377/job/36399386015#step:4:5177 |
Thanks, I'm having a look. |
This was an interesting one :) |
After upgrading to Quarkus 3.18.1, I see many warnings during Quarkus startup about unrecognized configuration keys related to quarkus-amazon-services.
You can find a reproducer at: https://github.com/steinsag/reproducer-quarkus-unrecognized-options
This will result in many warnings like:
Unrecognized configuration key "quarkus.ses.async-client.proxy.enabled" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo
As this is only happening for quarkus-amazon-services extensions, I assume something needs to be changed in extension definitions about config options.
The text was updated successfully, but these errors were encountered: