.env fail to read config property using numbers

[cescoffier]

Describe the bug

Let's imagine a .env file with the following content:

quarkus.tls.key-store.pem.acme.cert=/Users/clement/Downloads/code-with-quarkus/.letsencrypt/lets-encrypt.crt
quarkus.tls.key-store.pem.acme.key=/Users/clement/Downloads/code-with-quarkus/.letsencrypt/lets-encrypt.key

This one works (HTTPS enabled).

However, if I change the content to be:

quarkus.tls.key-store.pem.0.cert=/Users/clement/Downloads/code-with-quarkus/.letsencrypt/lets-encrypt.crt
quarkus.tls.key-store.pem.0.key=/Users/clement/Downloads/code-with-quarkus/.letsencrypt/lets-encrypt.key

It ignores the properties (only HTTP). I do not have any error or warning in the log.

PS: I'm using a packaged application (so not dev mode)

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

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 @radcortez (config)

[radcortez]

Hum, I've tried to use that configuration in .env and it seems to be read correctly:

[cescoffier]

Hum, this is weird; it ignored it for me while using 999-SNAPSHOT (maybe a slightly older version from one week or two).

Anyway, good to see it covered.