MongoDB active/inactive profile behavior

[zanmagerl]

Hi,
Quarkus 3.32 (#51013) introduced capability to disable default MongoDB client: https://quarkus.io/guides/mongodb#activate-or-deactivate-mongo-clients.
This allows you to disable client in case you will create it dynamically "by hand". The problem is that even if I set active: false, it still tries to encode/parse connection string and throws an error in case connection string is not valid:

Failed to start quarkus
at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)
at io.quarkus.runtime.Application.start(Application.java:112)\
at io.quarkus.runtime.ApplicationLifecycleManager.run(ApplicationLifecycleManager.java:127)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:79)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:50)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:143)
at io.quarkus.runner.GeneratedMain.main(Unknown Source)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:565)
at io.quarkus.runner.bootstrap.StartupActionImpl$1.run(StartupActionImpl.java:156)
at java.base/java.lang.Thread.run(Thread.java:1474)
Caused by: java.lang.IllegalArgumentException: URLDecoder: Incomplete trailing escape (%) pattern
at java.base/java.net.URLDecoder.decode(URLDecoder.java:219)

In our case we pass connection string such as: mongodb://%s:%s@x.y.z.w.... as we use that as template to replace it with username & password to get the final connection string that is then passed to the manually constructed client (MongoClientSettings settings = MongoClientSettings.builder().applyConnectionString()...).

Is this expected behavior? We can do a workaround, but from the documentation I thought that feature would enable us to use the connection-string property.

[quarkus-bot[bot]]

/cc @loicmathieu (mongodb)