Within the readme, the MQTT username is declared as "mqtt.username" in sourcecode it is defined as "mqtt.userName". If you configure the connector manually it is usually not a blocker. In my case i have written a small tool to provide AsyncAPI Bindings automatically into the related infrastructure (kafka & consul) with a mixture between the confluent mqtt sink and source connector (using the regex pattern) and this one here (because it solves a problem to switch topic name between kafka and mqtt in a sink configuration). I built a workaround within the provisioner that fixes the difference for me, so that is really a problem.
A small issue with very low priority.
Within the readme, the MQTT username is declared as "mqtt.username" in sourcecode it is defined as "mqtt.userName". If you configure the connector manually it is usually not a blocker. In my case i have written a small tool to provide AsyncAPI Bindings automatically into the related infrastructure (kafka & consul) with a mixture between the confluent mqtt sink and source connector (using the regex pattern) and this one here (because it solves a problem to switch topic name between kafka and mqtt in a sink configuration). I built a workaround within the provisioner that fixes the difference for me, so that is really a problem.
Best Regards