Convert mongodb-client to use @ConfigMapping

[mcruzdev]

Part of #45446

[mcruzdev]

ccompile error

[github-actions]

🎊 PR Preview d656dc3 has been successfully built and deployed to https://quarkus-pr-main-46070-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[gsmet]

Looks good overall but I noticed a small issue.

Could you adjust and squash the commits?

Thanks!

[gsmet]

We want Optional<@WithConverter(TrimmedStringConverter.class) String> and same for the other occurrences.

[gsmet]

Sorry we collided :).

[gsmet]

I will finalize things.

[gsmet]

It should be all good now and I rebased to get the CI fix.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit a620f6a.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit a620f6a.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[tms0]

Hi @mcruzdev, @gsmet,

I am the maintainer of the quarkus-mongock extension. I just noticed that this change breaks the build of the extension : https://github.com/quarkiverse/quarkus-mongock/actions/runs/13150659666/job/36704570744

I wonder how can I take this change into account in a backward-compatible way?

Thanks,
Valentin

[gsmet]

@tms0 hey. We will communicate much larger about this soon. Roberto sent an email yesterday on quarkus-dev and I was going to have a look at the Ecosystem CI failures today.

Unfortunately, this is a bit of a big bang change. We know it's not ideal but we really need to move to this new infrastructure.

We could have the option of restoring just enough old config (I think you just need the database name) for a couple of months but we will drop the old infrastructure at some point anyway so I'm not sure it's worth it. I checked if there could be other alternatives but I don't see anything that could provide you with the database name.

I don't know if your extension evolves a lot, do you think you could move main to use 3.19 when we release 3.19.0 and create a branch for older releases? Or would it be too uncomfortable?

Thanks for reaching out :).

[gsmet]

@tms0 that being said, you could use an approach similar to what @gastaldi did here: https://github.com/quarkiverse/quarkus-ironjacamar/pull/158/files#diff-546c20e149ef134f4ad79befb3f960d9ef06f1945aea77fdfd92fdd9cf845880R128-R130 .

Ideally you would get back to using proper config mapping in the future but it could ease the transition.