Serhii Vasylenko

Apparently, the `helm` provider (when configured in the same way) does not have this issue. So I can have the helm resources described in TF when the cluster does not...

My workaround for this issue: ```hcl provider "helm" { repository_config_path = "${path.module}/.helm/repositories.yaml" repository_cache = "${path.module}/.helm" kubernetes { host = module.cluster_linux.cluster_endpoint cluster_ca_certificate = base64decode(module.cluster_linux.cluster_ca[0].data) token = data.aws_eks_cluster_auth.this.token } } ```

@red8888, these two strings instruct the provider to look and use the `.helm` folder in the same directory where you call Terraform, assuming this is your root (aka project directory)...

IMO, it's okay to have such a resource in Terraform. Because from the AWS point of view, the Invalidation is not just a record in the log. It is a...