Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-709

configMap configured in quarkus.openshift properties does not get picked up by Quarkus application

XMLWordPrintable

    • False
    • False
    • +
    • Undefined
    • Workaround Exists
    • Hide

      Add quarkus.openshift.env.vars.smallrye-config-locations=</PATH/TO/MOUNTED/CONFIGMAP> to application.properties.

      Show
      Add quarkus.openshift.env.vars.smallrye-config-locations=</PATH/TO/MOUNTED/CONFIGMAP> to application.properties .
    • Hide

      1. Clone https://github.com/quarkus-qe/quarkus-openshift-test-suite
      2. Run `configMap` tests to reproduce the issue:

      mvn -B -V clean verify -pl app-metadata/deployment,app-metadata/runtime,common,configmap/file-system
      Show
      1. Clone https://github.com/quarkus-qe/quarkus-openshift-test-suite 2. Run `configMap` tests to reproduce the issue: mvn -B -V clean verify -pl app-metadata/deployment,app-metadata/runtime,common,configmap/file-system
    • ---

      configMap 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 configMap s:

      quarkus.openshift.config-map-volumes.app-config.config-map-name=app-config
quarkus.openshift.mounts.app-config.path=/deployments/config

      It seems that with Quarkus 1.11, a new property is required:

      quarkus.openshift.env.vars.smallrye-config-locations=/deployments/config

              gandrian Georgios Andrianakis
              mjurc@redhat.com Michal Jurc
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: