Prefix kafka consumer client.id with quarkus.application.name

[mrickly]

Description

• The auto-configuration of the client.id is described here: https://quarkus.io/guides/kafka#incoming-channel-configuration-polling-from-kafka
• The client.id is displayed for instance in the Clients dashboard of https://confluent.cloud/
• In order to distinguish the clients, we would have to prefix every channel with the quarkus.application.name
• It seems simpler to let quarkus prefix the client.id with the quarkus.application.name (and it would be consistent with the auto-configuration of the group.id).

Implementation ideas

No response

[quarkus-bot]

/cc @alesj, @cescoffier, @ozangunalp

[cescoffier]

Can't you set the client id explicitly in your application using ${quarkus.application.name}-your-id?

I'm not against that change, but it's a breaking change. So, we need to have an attribute to change the behavior (which would be another attribute, that's why my initial proposal could work as it is.)

[mrickly]

Sure we could. I'd rather not force every developing team to configure it explicitly for each incoming channel in their application though. We do pre-configure certain properties in our own extensions (quarkus-extension.yaml). However I don't see how that would work with variable channels... Maybe you have an idea how it could be done?

A non-breaking variant would be to add a prefix property with a "" default which would be applied to all client ids.

[cescoffier]

I like your proposal. We could define a global prefix attribute, and if the prefix is configured, it will be prepended.

@ozangunalp WDYT?

[ozangunalp]

This needs to be done in Smallrye Reactive Messaging.
Here is my proposal : smallrye/smallrye-reactive-messaging#1909

[cescoffier]

Fixed by #28117.