Kafka configuration using configuration profiles doesn't work

[jamesfalkner]

Describe the bug
When I use configuration profile prefixes in my application.properties like %prod to prefix Kafka settings it doesn't seem to pick it up when run as a fat JAR in a container, even though Quarkus claims at starting that it's running with the prod profile. Depending on which Kafka settings I prefix with %prod my application never initializes mediators during startup with Impossible to bind mediators, some mediators are not connected or tries to use localhost when my non-localhost bootstrap-servers settings are prefixed with %prod.

This happens even with the code from the guide at https://quarkus.io/guides/kafka-guide

Expected behavior
Kafka mediators and connections are properly established. When running in prod profile, config values prefixed with %prod. should be in effect and used to configure extensions like Kafka.

Actual behavior
Quarkus appears to ignore settings prefixed with %prod. even when in prod mode (i.e. fat JAR or native build).

To Reproduce
Steps to reproduce the behavior:

1. Follow the guide at https://quarkus.io/guides/kafka
2. Prefix all the Kafka settings from application.properties with %prod.
3. Run the app under prod mode instead of dev mode: either build a FAT jar and run with java -jar, or build a native image and run that (I have not tried dev mode with -Dquarkus.profile=prod).
4. Try to access app (names.html)
5. Observe failures in console.

Configuration

# Add your application.properties here, if applicable.
%prod.mp.messaging.outgoing.generated-name.bootstrap.servers=names-cluster-kafka-bootstrap:9092
%prod.mp.messaging.outgoing.generated-name.connector=smallrye-kafka
%prod.mp.messaging.outgoing.generated-name.topic=names
%prod.mp.messaging.outgoing.generated-name.value.serializer=org.apache.kafka.common.serialization.StringSerializer

# Configure the Kafka source (we read from it)
%prod.mp.messaging.incoming.names.bootstrap.servers=names-cluster-kafka-bootstrap:9092
%prod.mp.messaging.incoming.names.connector=smallrye-kafka
%prod.mp.messaging.incoming.names.value.deserializer=org.apache.kafka.common.serialization.StringDeserializer

Screenshots

Environment (please complete the following information):

• Output of uname -a or ver:
  Linux workspacendi6xxlz93n3i2we.dockerimage-5b6f9497f4-x4zkg 4.18.0-80.4.2.el8_0.x86_64 #1 SMP Fri Jun 14 13:20:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

• Output of java -version:

openjdk version "1.8.0_212"
OpenJDK Runtime Environment (build 1.8.0_212-b04)
OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)

• GraalVM version (if different from Java):
  19.2.1 CE

• Quarkus version or git rev:
  1.0.0.CR1

Additional context

[edeandrea]

We should fix this sooner than later.

[gsmet]

@cescoffier have you seen this one? I wonder if we use the API taking into account the profiles in SmallRye Reactive Messaging?

[cescoffier]

There is a draft pr about config that would address this.

Note that smallrye reactive messaging cannot used a quarkus specific API.

[machi1990]

#5387 which has just been merged fixed config related issues including this one.

@jamesfalkner do you mind trying the upstream master to see if this is indeed fixed? Thanks

[cescoffier]

It has been fixed.