Closed as duplicate of#40250
Description
Description
Hi, through testing in our lab, we have found that using quarkus.profiles the behavior has changed between versions 25 and 26. In 25 and earlier, if defining a value for https-port using a quarkus profile it is working but from 26 the value is not working.
To recreate use either '--profile=porttest 'in the command line start or set it in quarkus.properties, quarkus.profile=porttest, then in the keycloak.conf use the profile as follows %porttest.https-port=11000. You then see in the startup log '[io.quarkus] (main) Profile porttest activated.'
Do you know why this is, was there a change in 26, I cannot see anything in the release notes ?