Profile-specific parent profiles?

[edeandrea]

I was reading through the parent profile stuff in the Quarkus Configuration Reference. I would have expected to be able to assign a parent profile to specific child profiles.

For example, I don't seem to be able to do this:

quarkus.http.port=8084
%prod.quarkus.http.port=8080

%foo.quarkus.config.profile.parent=bar
%baz.quarkus.config.profile.parent=prod

Then if I built with -Dquarkus.profile=baz, I would expect the app's http port to be 8080, but instead the port is 8084.

Now, if I create an application-baz.properties file with the following content:

quarkus.config.profile.parent=prod

When I re-build with -Dquarkus.profile=baz, I now see the http port at 8080 like I would expect.

Is this a bug? In the main application.properties file, shouldn't I be able to assign a specific parent profile only for a certain child profile?

[edeandrea]

/cc @radcortez

[edeandrea]

Oh no worries at all!

[radcortez]

Hey @edeandrea

Right now, only a single level of the hierarchy is supported. If you feel that we should support multi-level, please open an enhancement request in https://github.com/smallrye/smallrye-config :)

[edeandrea]

Thanks @radcortez I may do just that!

And sorry about hitting you up last week - I completely forgot about how involved you are/were with JNation.

[radcortez]

No worries. All good :)

[edeandrea]

Created at smallrye/smallrye-config#767

[p1ass]

Does config profile support profile-specific parent profile when we use quarkus-config-yaml ?
I reproduce same unexpected behavior on Quarkus 2.9.2.

[p1ass]

Thank you for replying.
I understood quarkus.profile behavior and design background. 👍

I have a suggestion, how about adding a note in the documents that we can't use the parent profile in parent-aware files?

https://quarkus.io/guides/config-reference.html#parent-profile

[radcortez]

Can I ask you to submit a PR with it? :)

[p1ass]

Sure! I'll send a PR later.

[radcortez]

Great! Thanks!

[p1ass]

Submitted a pull request #26350