application-it.yaml ignored in IT native build

[vsevel]

Describe the bug

I am trying to use quarkus.test.integration-test-profile
I have a src/main/resources/application.properties with:

quarkus.test.integration-test-profile=it
quarkus.native.resources.includes=application-it.properties

and a src/main/resources/application-it.properties with:

foo=bar

and a endpoint:

@Path("/hello")
public class GreetingResource {

    @ConfigProperty(name = "foo", defaultValue = "xx")
    String foo;

    @GET
    @Produces(MediaType.TEXT_PLAIN)
    @Path("/foo")
    public String foo() {
        return foo;
    }
}

and my tests:

@QuarkusTest
class GreetingResourceTest {

    @Test
    void testProp() {
        given()
                .when().get("/hello/foo")
                .then()
                .statusCode(200)
                .body(is(getFoo()));
    }

    protected String getFoo() {
        return "xx";
    }
}

@QuarkusIntegrationTest
class GreetingResourceIT extends GreetingResourceTest {

    protected String getFoo() {
        return "bar";
    }
}

this works fine with:

mvn package => OK (found 'xx')
mvn verify -DskipITs=false => OK (found 'bar')

but it fails if I do:

mvn verify -Pnative => KO (found 'xx')

if I remove file application-it.properties and use application.properties as:

quarkus.test.integration-test-profile=it

%it.foo=bar

then the native IT works (found 'bar').

Expected behavior

should find 'bar'

Actual behavior

find the default value 'xx'.

How to Reproduce?

https://github.com/TechAndOperations/quarkus_reproducers/tree/issue-application-it-ignored

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

3.25.0

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[vsevel]

cc @radcortez

[radcortez]

I'll have a look

[radcortez]

In this case, you are trying to access a profile file that was not included in the native image build. It does work in JVM mode because all application source files are available. In native image, we only record / register the active pieces. By default, the native image build is built with the prod profile.

Checking the full logs, you should see something like:

[io.qua.run.con.ConfigRecorder] (main) The profile 'prod' used to build the native image is different from the runtime profile 'it'. This may lead to unexpected results.

My recommendation is to include the it profile when building the native image: mvn verify -Pnative -Dquarkus.profile=prod,it. This works.

[vsevel]

I was expecting %it.foo=bar to be equivalent to application-it.yaml.
this what I understood from https://quarkus.io/guides/config-reference#profile-aware-files
I can see the warning now: Do not use profile-aware files to set quarkus.profile or quarkus.test.profile. This will not work because the profile is required in advance to load the profile-aware files.
is this the reason why it is not working? in other words, does this apply to quarkus.test.integration-test-profile as well?
what does it mean it is needed in advance? being in src/main/resources, I guessed this was as available as it could be.

we can't really do mvn verify -Pnative -Dquarkus.profile=prod,it, because this would leak it properties into the app.

@ApplicationScoped
public class Startup {

    @ConfigProperty(name = "foo", defaultValue = "xx")
    String foo;

    void onStart(@Observes StartupEvent ev) {
        Log.info("foo=" + foo);

> mvn clean package -Pnative -DskipTests
> ./...-runner
2025-08-12 13:44:31,280 INFO  [org.acm.Startup] (main) foo=xx     <==============
2025-08-12 13:44:31,307 INFO  [io.quarkus] (main) profile-it 1.0.0-SNAPSHOT native (powered by Quarkus 3.25.0) started in 0.205s. Listening on: http://0.0.0.0:8080
2025-08-12 13:44:31,307 INFO  [io.quarkus] (main) Profile prod activated.

and

> mvn clean package -Dquarkus.profile=prod,it -Pnative -DskipTests
> ./...-runner
2025-08-12 13:50:26,284 INFO  [org.acm.Startup] (main) foo=bar    <==============
2025-08-12 13:50:26,292 INFO  [io.quarkus] (main) profile-it 1.0.0-SNAPSHOT native (powered by Quarkus 3.25.0) started in 0.045s. Listening on: http://0.0.0.0:8080
2025-08-12 13:50:26,293 INFO  [io.quarkus] (main) Profiles it,prod activated.

but that does not surprise you.
this would be acceptable if we would build one native app for testing (with profiles it end prod), and one, which we would package and release. but we would have to create 2 native apps, which we don't do.
we try to build the native app once, and start it with some config for testing.

the only approach I could find so far is this one: https://quarkus.io/guides/building-native-image#profiles
I was hoping I could use a custom profile, but without properties leaking into the built executable.
so at this point the only option would be to use %it.foo=bar (which is not ideal when you want to separate prod/test properties).
and there is no way we can improve this by supporting src/main/resources/application-it.properties?

[radcortez]

I can see the warning now: Do not use profile-aware files to set quarkus.profile or quarkus.test.profile. This will not work because the profile is required in advance to load the profile-aware files.
is this the reason why it is not working? in other words, does this apply to quarkus.test.integration-test-profile as well?
what does it mean it is needed in advance? being in src/main/resources, I guessed this was as available as it could be.

No, this is not the case for quarkus.test.integration-test-profile, because this doesn't set the profile directly, but instead sets a quarkus.profile in the test runner process.

When we build the native image, we only include what we need. So, in the case of profile-aware files, only the content of the active profiles during native image build is included in the final binary. The difference here is how a JAR build and Native build works... in a Native build, we need to register explicitly all resources we want to include in the native executable.

To include all profile-aware files, you can set quarkus.native.resources.includes=*.properties (or just list the main one and the it one), and this will also work without having to build with the it profile.

I was hoping I could use a custom profile, but without properties leaking into the built executable.

Not exactly sure if I understand here. In my view, there is always going to be a leakage of the properties, because for this to work, the it properties must be part of the native executable. Couldn't you set the additional properties in external files with quarkus.config.locations?

[vsevel]

To include all profile-aware files, you can set quarkus.native.resources.includes=*.properties (or just list the main one and the it one), and this will also work without having to build with the it profile.

which I believe I did: https://github.com/TechAndOperations/quarkus_reproducers/blob/issue-application-it-ignored/src/main/resources/application.properties#L2
you can actually see it at the app startup:

2025-08-14 06:41:46,851 INFO  [org.acm.Startup] (main) application.properties => null
2025-08-14 06:41:46,851 INFO  [org.acm.Startup] (main) application-it.properties => resource:/application-it.properties

I still do not understand why %it.foo=bar in application.properties vs foo=bar in application-it.properties are not functionaly equivalent in IT when specifying quarkus.test.integration-test-profile=it.
just to be clear, if I use %it.foo=bar it works as expected even in native. if I use application-it.properties it does not.
did I miss anything?

Not exactly sure if I understand here. In my view, there is always going to be a leakage of the properties, because for this to work, the it properties must be part of the native executable.

if I execute:

> mvn verify -Pnative -Dquarkus.profile=prod,it
> docker run -p 18080:8080 -it --rm sevel/profile-it:1.0.0-SNAPSHOT
...
2025-08-14 06:54:54,400 INFO  [io.quarkus] (main) Profiles it,prod activated.      <=== I do not want the it profile here
...

> curl localhost:18080/hello/foo
bar <========= this should be 'xx'

even if I run:

> docker run -p 18080:8080 -it --rm -e QUARKUS_PROFILE=prod  sevel/profile-it:1.0.0-SNAPSHOT
...
2025-08-14 06:59:07,561 INFO  [io.quarkus] (main) Profile prod activated.     <===== this is good
...

>  curl localhost:18080/hello/foo
bar      <====== this should be 'xx'

that is what I called properties used for IT leaking into the app.

Couldn't you set the additional properties in external files with quarkus.config.locations

that is what we are doing right now, but I think this is cleaner to work with profiles.
and I do not see how to use an application-it.properties

is there a way to use props in src/main/resources/application-it.properties in native and activate them during IT, and get them to be ignored (I do not care if I need to include the file in the native resources) when running the app in production with the default profile, just like I can do with %it.foo=bar ?

[radcortez]

which I believe I did: https://github.com/TechAndOperations/quarkus_reproducers/blob/issue-application-it-ignored/src/main/resources/application.properties#L2 you can actually see it at the app startup:

2025-08-14 06:41:46,851 INFO  [org.acm.Startup] (main) application.properties => null
2025-08-14 06:41:46,851 INFO  [org.acm.Startup] (main) application-it.properties => resource:/application-it.properties

I still do not understand why %it.foo=bar in application.properties vs foo=bar in application-it.properties are not functionaly equivalent in IT when specifying quarkus.test.integration-test-profile=it. just to be clear, if I use %it.foo=bar it works as expected even in native. if I use application-it.properties it does not. did I miss anything?

In native image mode, the application.properties content is encoded directly into the binary, meaning that there is no file anymore at runtime (same for application-aware files which have their profile active during the build). In this case, because we are manually including the file, you also need to include application.properties manually due to how loading of these file work:
https://quarkus.io/guides/config-reference#profile-aware-files

that is what I called properties used for IT leaking into the app.

Ok, because I would also consider having application-it.properties inside the binary to be a leaking issue.

is there a way to use props in src/main/resources/application-it.properties in native and activate them during IT, and get them to be ignored (I do not care if I need to include the file in the native resources) when running the app in production with the default profile, just like I can do with %it.foo=bar ?

Yes, by setting quarkus.native.resources.includes=*.properties or quarkus.native.resources.includes=application.properties,application-it.properties (the main file must always be there)

Alternatively, you could add these files to an external config folder, relative to the working dir (usually the project base dir):
https://quarkus.io/guides/config-reference#configuration-sources

In this case, you don't need quarkus.native.resources.includes, but you still need a main application.properties file.

[vsevel]

(the main file must always be there)

ahh. now I get it. this is exactly what I needed/was missing. thanks for re-detailing.
so I tried in application.properties:

quarkus.test.integration-test-profile=it
quarkus.native.resources.includes=application.properties,application-it.properties

and with the appropriate application-it.properties , I now have the IT build passing with just: mvn verify -Pnative and when I run the container with no profile options, I see the appropriate values:

2025-08-14 09:53:24,426 INFO  [org.acm.Startup] (main) application.properties => resource:/application.properties
2025-08-14 09:53:24,427 INFO  [org.acm.Startup] (main) application-it.properties => resource:/application-it.properties
2025-08-14 09:53:24,427 INFO  [org.acm.Startup] (main) application-toto.properties => null
2025-08-14 09:53:24,427 INFO  [org.acm.Startup] (main) foo=xx

Ok, because I would also consider having application-it.properties inside the binary to be a leaking issue.

I completely agree. but it seems to be a popular practice to include a bunch of application-xx.properties in src/main/resources (the application-dev.properties to begin with), and people do not seem bothered that in theory somebody could activate the dev profile in production.

Alternatively, you could add these files to an external config folder, relative to the working dir

thanks for pointing this out. but this configuration would be used for both QuarkusTest and QuarkusIntegrationTest. I was trying to come up with a scheme where you have a specific configuration for the app being launched during IT.

so many possibilities ;-)
I am going to make a few more tests to find the best solution.

[vsevel]

can you explain the difference between quarkus.test.native-image-profile and quarkus.test.integration-test?
is quarkus.test.native-image-profile the same as quarkus.test.integration-test, but only for native?

[radcortez]

thanks for pointing this out. but this configuration would be used for both QuarkusTest and QuarkusIntegrationTest. I was trying to come up with a scheme where you have a specific configuration for the app being launched during IT.

Yes, in that case, you could go with quarkus.config.locations just for the integration-tests to add additional search paths. It also supports directories, so you can have something like it-config/application.properties and it-config/application-it.properties and set quarkus.config.locations=it-config/

can you explain the difference between quarkus.test.native-image-profile and quarkus.test.integration-test?
is quarkus.test.native-image-profile the same as quarkus.test.integration-test, but only for native?

Yes, but they were unified here: #47759

[vsevel]

It also supports directories

interesting. I did not know about that. thanks.

Yes, but they were unified here: #47759

FYI it is still being part of the documentation:
https://quarkus.io/guides/building-native-image#profiles