Constantin Bugneac

Also ran into the same issue: ```bash Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress make: *** [Makefile:131: deploy] Error 1 ``` $ helm version version.BuildInfo{Version:"v3.5.3", GitCommit:"041ce5a2c17a58be0fcd5f5e16fb3e7e95fea622", GitTreeState:"dirty", GoVersion:"go1.16"}

What's strange - if I deploy `kafka_acls` resources - I don't get those warning but if I deploy topics - I do.

@larsbrekken just wondering have you been able to create a kind of `superadmin` user in MSK which has access to all topics upfront ? I'm struggling to understand how would...

Thanks a lot @larsbrekken Much appreciated. Do you know if this is required as well ? ```hcl resource "kafka_acl" "admin_cluster" { resource_name = "*" resource_type = "Cluster" acl_principal = "User:CN=admin-user"...

Thanks @larsbrekken

Giving some context: I'm using AWS MSK. It does return the broker list as: ``` broker1:9094,broker2:9094,broker3:9094 ``` Using `TF_VAR_name` would require mangling this connection string to transform it into: ```...

@cricket007 probably I wasn't clear enough. Terraform plan for MSK cluster returns: ``` Outputs: bootstrap_brokers_tls = b-2.infratest-test-msk.a3g3juk.c3.kafka.eu-west-1.amazonaws.com:9094,b-3.infratest-test-msk.a3g3juk.c3.kafka.eu-west-1.amazonaws.com:9094,b-1.infratest-test-msk.a3g3juk.c3.kafka.eu-west-1.amazonaws.com:9094 ``` That's how AWS TF provider returns the brokers. I would like to...

@cricket007 why it is a feature unrelated to this provider ? All other options of this provider do support env. variables. Just being consistent to have support for `BOOTSTRAP_SERVERS` will...

Looks like the public access for MSK cluster can be enabled if connecting from outside of VPC where it was originally deployed https://docs.aws.amazon.com/msk/latest/developerguide/public-access.html.

I agree, in local development/testing generating self signed certs is an overhead.