Describe the bugconfigMap configured in quarkus.openshift according to Quarkus - Deploying on OpenShift does not get properly recognised by a Quarkus application. This approach worked in 1.7, therefore this is a breaking change.
With Quarkus 1.7, using the properties from docs was sufficient for a RESTful Quarkus application to pick up configMaps:
Add quarkus.openshift.env.vars.smallrye-config-locations=/deployments/config to config-secret/file-system/src/main/resources/application.properties. Rerun test for workaround.
Describe the bug
configMap
configured inquarkus.openshift
according to Quarkus - Deploying on OpenShift does not get properly recognised by a Quarkus application. This approach worked in 1.7, therefore this is a breaking change.With Quarkus 1.7, using the properties from docs was sufficient for a RESTful Quarkus application to pick up
configMap
s:It seems that with Quarkus 1.11, a new property is required:
Expected behavior
configMap
is picked up by application deployed to OpenShift.Actual behavior
configMap
is not picked up by application deployed to OpenShift.To Reproduce
configMap
tests to reproduce the issue:quarkus.openshift.env.vars.smallrye-config-locations=/deployments/config
toconfig-secret/file-system/src/main/resources/application.properties
. Rerun test for workaround.Configuration
Screenshots N/A
Environment (please complete the following information):
uname -a
orver
:Linux tigris 5.10.8-200.fc33.x86_64 #1 SMP Sun Jan 17 19:53:01 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
java -version
:1.11.0.Final
mvnw --version
orgradlew --version
):Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T21:00:29+02:00)
Additional context (Add any other context about the problem here.)
https://github.com/quarkusio/quarkus/issues/14525
$upstream:14525$