Config properties of inactive profiles are being expanded in 1.6.0.CR1

[sirAlexander]

Describe the bug
Just tried this version of quarkus as there is a critical fix I need i.e #10215

but on running mvn quarkus:dev the application seems to ignore all Dev config in the application.properties i.e. %dev.quarkus .datasource..... and instead uses prod properties.

Seems like quite the regression. @geoand @gsmet

[geoand]

Very serious indeed, thanks for reporting!

I'll look into it, but I have a feeling that it might be caused by #9184. If that turns out to be true, I'll revert that PR

[geoand]

I was not able to reproduce the problem with either 1.6.0.CR1 or Quarkus from master.

Can you provide some more details @sirAlexander ?

[geoand]

Actually, let me try one more thing

[geoand]

I tried another thing:

quarkus.http.cors=false
%dev.quarkus.http.cors=true

and reading the value of io.quarkus.vertx.http.runtime.HttpConfiguration#corsEnabled in dev mode and it turned out to be false as expected.

I also tried a flyway example with

quarkus.flyway.migrate-at-start=false
%dev.quarkus.flyway.migrate-at-start=true

where again things worked as expected.
@sirAlexander can you provide a reproducer for the issue you are seeing?

[sirAlexander]

@geoand this is what I changed in my pom.xml, not sure if it is the correct way to do it

<quarkus-plugin.version>1.6.0.CR1</quarkus-plugin.version>
        <quarkus.platform.artifact-id>quarkus-bom</quarkus.platform.artifact-id>
        <quarkus.platform.group-id>io.quarkus</quarkus.platform.group-id>
        <quarkus.platform.version>1.6.0.CR1</quarkus.platform.version>

so using quarkus-bom instead of quarkus-universal-bom

[geoand]

That is correct. But since I am unable to reproduce the issue you are seeing, it would be great if you could provide a small reproducer project that exhibits this behavior.

[sirAlexander]

@geoand I've updated the reproducer here if that can help >> https://github.com/sirAlexander/quarkus-reproducer

running mvn quarkus:dev reproduces the issue

[geoand]

I'll take a look, thanks

[geoand]

OK, I understand what the problem is.

Basically Quarkus is trying to expand the env vars in:

quarkus.datasource.jdbc.url=jdbc:mysql://${DB_HOST}/${DB_NAME}

even though there is a dev mode property that overrides quarkus.datasource.jdbc.url:

%dev.quarkus.datasource.jdbc.url=jdbc:mysql://localhost:3306/web_analytics

So a simple workaround for the time being is to use quarkus.datasource.jdbc.url=jdbc:mysql://${DB_HOST:dummy}/${DB_NAME:dummy}

However I am in favor of reverting #9184 unless we can get a fix in for 1.6.0.Final. WDYT @radcortez, @gsmet ?