Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
rgl opened this issue Sep 11, 2023 · 4 comments
Labels

Comments

@rgl
Copy link

rgl commented Sep 11, 2023

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.

@rgl rgl added the question label Sep 11, 2023
@jrhouston
Copy link
Contributor

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

@rgl
Copy link
Author

rgl commented Sep 13, 2023

@triadcode
Copy link

triadcode commented Nov 12, 2023

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
Copy link

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

  • hashicorp/kubernetes v2.27.0 (signed by HashiCorp)
  • hashicorp/helm v2.12.1 (signed by HashiCorp)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants