I am faced with a situation in which multiple developers are working on specific kafka source or sink connector configurations. The connectors are created, updated, deleted, and so on via the kafka connect REST API. It must be assured that
connector.class
like for example "streams.kafka.connect.sink.Neo4jSinkConnector"Is there any way to configure Kafka to restrict the use of the Kafka-Connect REST API to specific operations related to connector configuration details? The kafka ACLs seem not to cover this usecase.
Kafka Connect offers Basic HTTP Auth with username/password support, but for "ownership" or "limited management" of Connectors, no, that feature doesn't really exist out of the box.
For this, you'd need to implement your own REST Extension(s).
Resources:
Or create your own "proxy server" that will do this and forward requests to the Connect API.
Other option would be to let said developers deploy and maintain their own Connect Clusters, such as via containers in Kubernetes or Terraform some cloud VMs.