Unable to find properties when using profile files

[svemis]

When using application.properties per profile:

application-dev.properties
application-test.properties
application-prod.properties

As indicated here --> https://quarkus.io/guides/config-reference#profile-aware-files

The specific properties required for this plugin are not found, returning:

Caused by: io.quarkus.runtime.configuration.ConfigurationException: One or more configuration errors have prevented the application from starting. The errors are:

• SRCFG00014: The config property quarkus.log.cloudwatch.access-key-id is required but it could not be found in any config source
• SRCFG00014: The config property quarkus.log.cloudwatch.access-key-secret is required but it could not be found in any config source
• SRCFG00014: The config property quarkus.log.cloudwatch.region is required but it could not be found in any config source
• SRCFG00014: The config property quarkus.log.cloudwatch.log-group is required but it could not be found in any config source
• SRCFG00014: The config property quarkus.log.cloudwatch.log-stream-name is required but it could not be found in any config source

[bennetelli]

@svemis Thanks for your PR. We are working in a different way to solve environment specific entries, but I will reproduce it and fix your issue as soon as I have got time. Thanks for raising it :)

[bennetelli]

hey @svemis,

I just found this issue: quarkusio/quarkus#18375
I would say this is not an issue with the extension, rather an issue with Quarkus itself.

[bennetelli]

I would like to close this issue as Quarkus has been designed with a single profile in mind.

[gwenneg]

Quarkus does support multiple profiles and the use case mentioned in this issue is completely valid.

@svemis I did a quick test with a setup similar to what you described. The extension started normally and picked the config values from the separate profile file. Could you please check that Quarkus starts with the correct profile while the extension is disabled at first, before trying again with the extension enabled? The active profile will be showed at startup in the following log line:

2023-01-17 09:15:50,189 INFO  [io.quarkus] (main) Profile gwenneg activated.

It is possible that your app started with the wrong one, preventing this extension from loading its config values.

You can activate a profile by setting the QUARKUS_PROFILE environment variable to any value you need.

[bennetelli]

Let's reopen it until we get a response.