Docs: Disparities between the online quarkus-messaging-kafka extension docs

[darbyredhat]

Describe the bug

This was reported by a customer.

I am seeing many disparities between the online quarkus-messaging-kafka extension docs and reality. The docs are incorrect about configuring the quarkus devservice; the runtime container reports that the several documented config elements are invalid, e.g., "Unrecognized configuration key quarkus.kafka.devservices.topics\ ...

... the documentation that still refers to the “mp…” config elements that were in the smallrye extension, Apache Kafka Reference Guide - Quarkus. When quarkus docs have a banner that says a newer version of an extension is available, SmallRye Reactive Messaging - Kafka Connector | Extensions, but the new version points to the old docs, Getting Started to Quarkus Messaging with Apache Kafka - Quarkus.

Expected behavior

The docs should match the Quarkus runtime behavior.

Actual behavior

Runtime container reports that the several documented config elements are invalid, e.g., "Unrecognized configuration key quarkus.kafka.devservices.topics\

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 @alesj (kafka), @cescoffier (kafka), @ozangunalp (kafka)

[cescoffier]

Thanks for reporting this!
Do you have the list of inconsistencies? Are they all about configuration properties?

[gsmet]

I had a look and I don't think we are pointing to an old guide.

Quarkus Messaging uses SmallRye Reactive Messaging under the hood. So if something looks old, could we clarify what exactly?

Then, I'm not exactly sure what quarkus.kafka.devservices.topics\ refers to. Could we have the full name of the property? Because this is not a valid property.

[ozangunalp]

The correct build-time property to configure topics to create for the Kafka dev service is quarkus.kafka.devservices.topic-partitions.[topic-name]=[partition-count]