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

Warnings about unrecognized config keys after upgrade to Quarkus 3.18.1 #1564

Open
steinsag opened this issue Jan 30, 2025 · 7 comments
Open

Comments

@steinsag
Copy link

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

./mvnw clean test

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.

@steinsag
Copy link
Author

The problem can also be seen in the dependabot build for upgrading this repo to Quarkus 3.18.1:

https://github.com/quarkiverse/quarkus-amazon-services/actions/runs/13047086377/job/36399386015#step:4:5177

@gsmet
Copy link
Member

gsmet commented Jan 30, 2025

/cc @radcortez

@radcortez
Copy link

I'll have a look

@radcortez
Copy link

@steinsag I'm getting a 404 with the reproducer. Maybe it is private?

@steinsag
Copy link
Author

@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

@radcortez
Copy link

Thanks, I'm having a look.

@radcortez
Copy link

This was an interesting one :)

smallrye/smallrye-config#1298

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

No branches or pull requests

3 participants