Openshift deployment config properties all start with get-/is-

[yrodiere]

Describe the bug

In the documentation at least, it seems config properties are broken, as they all start with get-/is-:

See screenshot from the documentation of the main branch:

Branch 3.3 seems affected as well, not sure about 3.2. 2.x isn't affected for sure.

I'm not sure whether this is just a documentation problem, or if configuration properties are actually broken.

Expected behavior

No weird get-/is- prefixes.

Actual behavior

Weird get-/is- prefixes.

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @geoand (openshift), @iocanel (openshift)

[yrodiere]

See also https://quarkusio.zulipchat.com/#narrow/stream/187038-dev/topic/Openshift.20deployment.20config

[gsmet]

@radcortez that's probably another one for you?

[gsmet]

The particularity of this config is that there are getters in it. And that might conflict with the detecting of the new @ConfigMapping stuff.

I'll have a look to see if I can figure out how to work around it.

[yrodiere]

Note this seems to impact other, related extensions, e.g. the Kubernetes one: https://quarkus.io/guides/deploying-to-kubernetes#quarkus-kubernetes-kubernetes-config_quarkus.kubernetes.get-env.secrets

[gsmet]

Yeah, I noticed that.

[gsmet]

I created a PR here: #35618 .

It also affects 3.2.