hashicorp / terraform-provider-helm

Terraform Helm provider
https://www.terraform.io/docs/providers/helm/
Mozilla Public License 2.0
1k stars 371 forks source link

Provider produced an invalid plan for x, but we are tolerating it because it is using the legacy plugin SDK #1248

Open rgl opened 1 year ago

rgl commented 1 year ago

If you prefer, you can also ask your question in the Kubernetes community Slack channel #terraform-providers. (Sign up here)

Terraform version, Kubernetes provider version and Kubernetes version

Terraform version: 1.5.7
Helm Provider version: 2.11.0
Kubernetes version: 1.26.6

Terraform configuration

# not applicable

Question

Should I be worried about the following log message?

Provider "registry.terraform.io/hashicorp/helm" produced an invalid plan for helm_release.kubernetes_dashboard, but we are tolerating it because it is using the legacy plugin SDK.

jrhouston commented 1 year ago

Thanks for opening an issue @rgl – can you share the config that produced this output message?

rgl commented 1 year ago

It's at https://github.com/rgl/terraform-azure-aks-example

triadcode commented 1 year ago

I believe I do have the same issue with the following: helm provider v2.11 (tried also with 2.9) kubernetes provider v2.23.0 kubernetes version 1.25 terraform version v1.6.3

My code is the following:

resource "helm_release" "nginx-ingress" {
  name  = "ingress-nginx"
  chart   = "ingress-nginx"
  repository = "https://kubernetes.github.io/ingress-nginx"
  namespace = "ingress"
  create_namespace = true
  version = "4.8.3"
}

In the plan that has been generated, the version is replaced with 1.0.0 and running with TF_LOG=trace. I get the following output:

[WARN]  Provider "registry.terraform.io/hashicorp/helm" produced an invalid plan for helm_release.nginx-ingress, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .reset_values: planned value cty.False for a non-computed attribute
      - .atomic: planned value cty.False for a non-computed attribute
      - .reuse_values: planned value cty.False for a non-computed attribute
      - .timeout: planned value cty.NumberIntVal(300) for a non-computed attribute
      - .max_history: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .replace: planned value cty.False for a non-computed attribute
      - .skip_crds: planned value cty.False for a non-computed attribute
      - .verify: planned value cty.False for a non-computed attribute
      - .cleanup_on_fail: planned value cty.False for a non-computed attribute
      - .pass_credentials: planned value cty.False for a non-computed attribute
      - .dependency_update: planned value cty.False for a non-computed attribute
      - .lint: planned value cty.False for a non-computed attribute
      - .render_subchart_notes: planned value cty.True for a non-computed attribute
      - .disable_crd_hooks: planned value cty.False for a non-computed attribute
      - .version: planned value cty.StringVal("1.0.0") does not match config value cty.StringVal("4.8.3")
      - .wait: planned value cty.True for a non-computed attribute
      - .wait_for_jobs: planned value cty.False for a non-computed attribute
      - .disable_webhooks: planned value cty.False for a non-computed attribute
      - .recreate_pods: planned value cty.False for a non-computed attribute
      - .disable_openapi_validation: planned value cty.False for a non-computed attribute
yohikofox commented 7 months ago

Plop, I'm currently encountering this error message. Don't close it please

evanvolgas commented 2 months ago

I'm also running into this message and I believe it's causing my dagster-user-deployments chart to fail