search

confluentinc / terraform-provider-confluent

Terraform Provider for Confluent
Apache License 2.0
27 stars 63 forks source link

Ability to manage Schema Registry ACLs #264

Open jmjesperson opened 1 year ago

jmjesperson commented 1 year ago

Similar to managing Kafka cluster ACLs in Terraform with the resource confluent_kafka_acl.

I want the ability to manage Schema Registry Cluster ACLS via Terraform. Currently, the only way I can manage these are via the Confluent Cloud UI or Schema Registry ACL Authorizer.

0angelic0 commented 1 year ago

+1

Just encountered the issue. Could not find a way to manage schema registry ACL from the doc (https://registry.terraform.io/providers/confluentinc/confluent/latest/docs/resources/confluent_api_key) after created a service account and a schema registry api key. Then found this github issue.

jmjesperson commented 1 year ago

+1

Just encountered the issue. Could not find a way to manage schema registry ACL from the doc (https://registry.terraform.io/providers/confluentinc/confluent/latest/docs/resources/confluent_api_key) after created a service account and a schema registry api key. Then found this github issue.

My work around has been to use Role Binding -> https://registry.terraform.io/providers/confluentinc/confluent/latest/docs/resources/confluent_role_binding

nickatnight commented 1 year ago

Is Role Binding still limited to basic cluster? From docs

Note: Basic Kafka cluster with authorization using RBAC configuration is not supported, because both DeveloperRead and DeveloperWrite roles are not available for Basic Kafka clusters.

skippaDaBitFlippa commented 9 months ago

+1 Just encountered the issue. Could not find a way to manage schema registry ACL from the doc (https://registry.terraform.io/providers/confluentinc/confluent/latest/docs/resources/confluent_api_key) after created a service account and a schema registry api key. Then found this github issue.

My work around has been to use Role Binding -> https://registry.terraform.io/providers/confluentinc/confluent/latest/docs/resources/confluent_role_binding

Do you still have to create a separate API key for that service account to access the schema registry? What credentials do you use when the role binding has been created for a service account?