as a developer, I’m wondering about the management of configuration properties in Quarkus. And in particular how to share (expose/contract) custom application properties that should be modified/valued in environments by ops.
Just as with OpenAPI-type contractualization, it would seem useful to have both the keys to be valued and the associated documentation, so as to know what the property is used for, in order to be able to value it correctly at runtime.