Aidan Melen

I was getting the same error. My work around was to do away with the repository and version arguments. Instead of this ```hcl resource "helm_release" "nginx_ingress" { name = "nginx-ingress"...

> With Helm 3, all releases metadata are saved as Secrets in the same Namespace of the release. Thank you Thank you! In my case, the AWS Token expired after...

@WheresAlice this would be nice for this provider; however, you should also consider using the [Confluent Config Provider](https://docs.confluent.io/platform/current/connect/security.html#externalizing-secrets) to externalize secrets. This prevent your secrets from being exposed in Kafka....

@citizenken have you experimented with the [wait_for_jobs](https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release#wait_for_jobs) or [cleanup_on_fail](https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release#cleanup_on_fail) resource arguments? Those might be useful in this case.

Hi @davidsloan I am experiencing a similar issue with a build from `master` and am wondering if it is related. The s3 source connector flushes all of the messages contained...

^^^ on second thought, this may be more related to https://github.com/lensesio/stream-reactor/issues/861

We got the same error...

Can we please update the Deb/Ubuntu packages to version 1.7.0? It would be great to have the new AVRO support in those packages.

https://github.com/strimzi/strimzi-kafka-operator/issues/5473

We are working on modifying the `kafka_connect_config_generator.sh` script to support `KAFKA_CONNECT_SASL_MECHANISM="aws"`. It would integrate with the AWS environments variables and fit nicely into the `spec.authentication.mechanism` CRD. To have full support...