How to use provider to configure connectors in Confluent Cloud cluster directly?

[askoriy]

All guides of using kafka connect say to run ./bin/connect-standalone providing connect-standalone.properties and then connect using url = "http://localhost:8083".
However, I noticed that for configuring connectors via GUI interface Confluent Cloud provides API endpoint:
https://confluent.cloud/api/accounts/{{ env_id }}/clusters/{{ cluster_id }}
The format of API is the same, however the difference is that Confluent Cloud API uses JWT token authorization, but terraform sends Authorization: Basic header. So Terraform can't authorize.

Is it possible to add JWT authorization so the provider could work directly with Confluent Cloud?

If I wrong please explain the way how to use the provider with Confluent Cloud?

[Mongey]

I think supporting arbitrary headers is probably a good idea.

[Marcus-James-Adams]

We would love this feature as we've just started using your excellent confluent cloud provided and are looking as work arounds for connecting the SQL cdc connector into it

[benweint]

This seems directly related to #41.

FWIW, I have a PR against the underlying Kafka Connect client library that adds the ability for it to pass along arbitrary headers (which I think would be a prerequisite for this work, unless we swap out or reimplement the underlying client lib).