Helm provider update broken components

[mtb-xt]

Hi team,

I think helm provider for terraform got updated, so now components and modules are failing:

See also here - hashicorp/terraform-provider-helm#1637
https://registry.terraform.io/providers/hashicorp/helm/latest/docs/guides/v3-upgrade-guide

The components either need to be updated, or in the mean time, pinned to 'less than 3.0'
https://github.com/cloudposse-terraform-components/aws-eks-external-dns/blob/ea4f563d7676db778efe1c6ae1a1be1a77314df5/src/versions.tf#L11

At the moment, all components which are trying to install a helm chart (external-dns, external-secrets, etc) are broken, and we had to modify the code ourselves.

Error: Unsupported block type

  on provider-helm.tf line 154, in provider "helm":
 154:   kubernetes {

Blocks of type "kubernetes" are not expected here. Did you mean to define
argument "kubernetes"? If so, use the equals sign to assign it a value.

Error: Unsupported block type

  on provider-helm.tf line 175, in provider "helm":
 175:   experiments {

Blocks of type "experiments" are not expected here. Did you mean to define
argument "experiments"? If so, use the equals sign to assign it a value.
ERRO exit status 1

[brucex]

i'm running into the same issue

[brucex]

@milldr looks like this issue has been opened for 5 days. Can someone from CP take a look? Thanks.

[osterman]

Apologies for the delay in getting back to both of you on this — we definitely dropped the ball here, and I hate that. Our internal SLA is two days, and it's been five. No excuses.

We’re actively rolling out the fix today across all of our components that depend on the Helm provider. The current workaround is to pin the provider to < 3.0.0 to avoid the breaking changes introduced in the latest release.

Here are some related conversations that might interest you:

• https://sweetops.slack.com/archives/CB6GHNLG0/p1750277409636419
• Pin provider versions of components using terraform required_providers  atmos#1194 (comment)

Thanks for your patience — we’ll do better.

[Benbentwo]

hey so this is because helm recently updated their provider releasing v3 . V3 is not backwards compatible and we're working to update all the components right now.

For example cloudposse-terraform-components/aws-eks-cert-manager#33

Full list of PRs

• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-datadog-synthetics-private-location#36
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-actions-runner-controller#31
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-addon#20
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-alb-controller#35
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-alb-controller-ingress-class#32
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-cert-manager#33
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-cloudwatch#18
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-echo-server#35
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-external-dns#32
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-external-secrets-operator#31
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-github-actions-runner#30
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-idp-roles#32
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-karpenter-controller#34
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-karpenter-node-pool#33
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-loki#30
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-metrics-server#33
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-node-termination-handler#29
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-prometheus-scraper#30
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-promtail#28
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-redis#32
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-redis-operator#29
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-reloader#35
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-spacelift-worker-pool#32
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-spacelift-worker-pool-controller#26
• chore(deps): restrict helm provider version to ~ 2.0.0 cloudposse-terraform-components/aws-eks-storage-class#28

Once these PRs are merged in it'll pin you to v2. We'll then work on an upgrade path for the components to v3.

Since this is most likely a blocker for you the easiest way forward would be to pin to v2 (matching the PR) so changing your versions.tf to something like

    helm = {
      source  = "hashicorp/helm"
      version = ">= 2.0.0, < 3.0.0"
    }

Then you'll need to run a clean (or manually delete the files of the cached v3 provider). For example atmos terraform clean <component> -s <stack>

[Benbentwo]

Hey @mtb-xt, Should be able to vendor in the latest now if you haven't updated already.

[mtb-xt]

Thank you