Marcus Adams

Whilst I can't help on the code side of adding the networking options, I can assist on the testing debugging or Azure-based Private Link and peering if it helps

@bono007 please excuse my ignorance as i am an infra guy rather than a dev - but does not this https://github.com/cgroschupp/go-client-confluent-cloud/blob/master/confluentcloud/cluster.go#L39 suggest that it is supported?

Not sure if it will help get things moving but I've put a request in against the go client - https://github.com/cgroschupp/go-client-confluent-cloud/issues/14 If people could add their votes to it.

Once again not being a dev but an infra guy i notice that confluent provide their own client https://github.com/confluentinc/confluent-kafka-go - Would it not make sense to wrap the terraform provider...

Just as its been some time, is there any movement on this?

Whilst I'm a bit late to the party, I too had the same error, after much blood sweat, and tears looking at the exported JSON and working out what resource...

this ties in with - #731 and - #732 If you are working on mappers for system-generated roles, you needto be able to read the scope as a data object...

From what I've read so far Kubernetes provides an API for attaching to the console of a container over the network. Since with K8s you can have more than one...

I was seeing it as passthrough. That way you could utilise the RDP gateway function on the client to keep it simple On Mon, 24 Feb 2020, 19:24 anazmy, wrote:...

I would also suggest generating it from terraform templates - that would be super usefull Regards Marcus On Mon, 2 Aug 2021 at 11:32, jmostella ***@***.***> wrote: > As part...