Describe the bug
quarkus.application.name seems overridable at runtime whereas it is flagged as fixed at build time within the docs
Expected behavior
The doc to reflect the fact that quarkus.application.name config property can be overridden at runtime
Actual behavior
The doc flags the quarkus.application.name config property as fixed at build time.
To Reproduce
Steps to reproduce the behavior:
quarkus.application.name config propertyQUARKUS_APPLICATION_NAME environment variable)Configuration
# Add your application.properties here, if applicable.
Screenshots
(If applicable, add screenshots to help explain your problem.)
Environment (please complete the following information):
uname -a or ver:java -version:mvnw --version or gradlew --version):Additional context
(Add any other context about the problem here.)
This is interesting for sure :)
Given the way you are using it (via @ConfigProperty) in this specific use case, your code will see the updated value.
However, that doesn't mean it's a runtime property, due the fact that the Quarkus extensions that actually use this value (the spring-cloud-config extension for example), will not use the runtime value, but the build time one.
That is what is meant by the fact that the property is build time and runtime visible.
OK thanks for clarifying
YW!
Most helpful comment
This is interesting for sure :)
Given the way you are using it (via
@ConfigProperty) in this specific use case, your code will see the updated value.However, that doesn't mean it's a runtime property, due the fact that the Quarkus extensions that actually use this value (the
spring-cloud-configextension for example), will not use the runtime value, but the build time one.That is what is meant by the fact that the property is build time and runtime visible.