[aws-load-balancer-controller]: terraform is broken trying to apply configuration second time

[mglotov]

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

• [X] I am running the latest version
• [X] I checked the documentation and found no answer
• [X] I checked to make sure that this issue has not already been filed

Expected Behavior

terraform apply command in layer2-k8s folder mustn't return an error if nothing changed.

Current Behavior

If you set aws_loadbalancer_controller_enable = true and run terraform apply twice in layer2-k8s folder, you get an error due to terraform helm provider (https://github.com/hashicorp/terraform-provider-helm/issues/711)

Failure Information (for bugs)

Error: Provider produced inconsistent final plan

When expanding the plan for
module.eks_alb_ingress[0].helm_release.aws_loadbalancer_controller to include new values
learned so far during apply, provider "registry.terraform.io/hashicorp/helm"
produced an invalid new value for .manifest: was
cty.StringVal("...long string-escaped JSON block of the old manifest..."),
but now
cty.StringVal("...long string-escaped JSON block of the new manifest...").

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

If you set for helm provider

experiments {
   manifest = false
}

you won't get the error above.

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. switch to layer2-k8s folder
2. set aws_loadbalancer_controller_enable = true
3. run terraform apply
4. run terraform apply again

Context

• Affected module version:
• OS:
• Terraform version: 0.15.1

Any other relevant info including logs

There is a workaround https://github.com/kubernetes-sigs/aws-load-balancer-controller/pull/2264, but it isn't available in the helm repo yet.

[mglotov]

Tried to use the latest version (1.4.1). The problem still exists