As discussed in #17389 our existing approach is not ideal. It would be nice if we could somehow expose all configuration options as "first-class" properties with metadata and, therefore, IDE auto-completion.

Comment From: MadJlzz

I've hit this point very recently after seeing that KafkaProperties was missing configuration properties. Apart from creating a "first-class" exposing all of Kafka properties like you mentionned, I don't know how you want to manage this... Sadly, I find this solution quite unmaintanable...

Comment From: Wzy19930507

Apache Kafka use org.apache.kafka.common.config.ConfigDef management peoperties metadate(key, doc, default value etc.). perhaps can create adaptor for mapping org.apache.kafka.clients.consumer.ConsumerConfig#configDef to spring.kafka.consumer.properties and mapping org.apache.kafka.clients.producer.ProducerConfig#configDef to spring.kafka.producer.properties