QuarkusUnitTest API to configure more than one .properties resource

[rquinio1A]

Describe the bug

Following #43129 and with 999-SNAPSHOT, it's no longer possible to call multiple times QuarkusUnitTest#withConfigurationResource, only the last resource is taken into account.

With Quarkus 3.15.1, it was possible to do this: https://github.com/quarkiverse/quarkus-logging-splunk/blob/a7fa1ae74ef2b8f031e4cadb095f81545289e062/deployment/src/test/java/io/quarkiverse/logging/splunk/LoggingSplunkMinimalConfigTest.java#L22-L23

I guess it might have been a mis-usage of the API ? Is there another way to pass more than one .properties resource per QuarkusUnitTest ?

/cc @mkouba

Quarkus version or git rev

999-SNAPSHOT (master)

[quarkus-bot]

/cc @radcortez (config)

[mkouba]

I guess it might have been a mis-usage of the API ? Is there another way to pass more than one .properties resource per QuarkusUnitTest ?

Well, the contract for QuarkusUnitTest#withConfigurationResource() was undefined before #43181 so it's not a misuse per se ;-).

We could add a method that would load the properties from the given file and then use the QuarkusUnitTest#overrideConfigKey() for each property. It should be called loadConfigProperties() or something along these lines.

[rquinio1A]

Thanks. If #withConfigurationResource behavior will remain as-is and it's a new method, I guess short-term I'll refactor my tests anyway to use #overrideConfigKey() or merge the .properties, as I don't want to maintain a specific 3.15 LTS branch just for a test change if I can avoid it.

[mkouba]

Thanks. If #withConfigurationResource behavior will remain as-is and it's a new method, I guess short-term I'll refactor my tests anyway to use #overrideConfigKey() or merge the .properties, as I don't want to maintain a specific 3.15 LTS branch just for a test change if I can avoid it.

👍 Sounds reasonable.

[HerrDerb]

Suggestion for a new method to override configs from a config source #44369