Handling bridge configuration together with Quarkus related one

Dealing with bridge configuration and Quarkus configuration. Right now we have all HTTP related bridge configuration in the config/application.properties file (see http prefixed properties). By moving to Quarkus some of the HTTP related configuration has to be set in the resources/application.properties (see quarkus.http prefixed properties) which can be overridden through -D system properties.

• How to deal with this difference?
• Can a custom Microprofile ConfigProvider help here?
• When the bridge starts from command line or is configured via the Strimzi operator, should we consider deprecating http prefixed configuration in the config/application.properties file and getting the quarkus.http on command line as system properties? (we cannot rely on the resources/application.properties file which is baked at build time).