Stale metadata output from previous release

[nitrocode]

Terraform, Provider, Kubernetes and Helm Versions

Terraform version: 1.4.2
Provider version: 2.9.0
Kubernetes version: 1.25

Affected Resource(s)

• helm_release

Terraform Configuration Files

resource "helm_release" "example" {
  name       = "my-redis-release"
  repository = "https://charts.bitnami.com/bitnami"
  chart      = "redis"
  version    = "6.0.1"

  values = [
    "${file("values.yaml")}"
  ]

  set {
    name  = "cluster.enabled"
    value = "true"
  }

  set {
    name  = "metrics.enabled"
    value = "true"
  }

  set {
    name  = "service.annotations.prometheus\\.io/port"
    value = "9127"
    type  = "string"
  }
}

output "metadata" {
  value = helm_release.example.metadata
}

Debug Output

NOTE: In addition to Terraform debugging, please set HELM_DEBUG=1 to enable debugging info from helm.

Panic Output

Steps to Reproduce

1. create new helm release
2. terraform apply
3. change values or release version
4. terraform apply

Notice the metadata output is from the prior apply. If we run apply again, it will show the newer metadata.

Expected Behavior

Actual Behavior

Important Factoids

References

• https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release#metadata
• similar to Metadata attribute does not act as a computed attribute #1093

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[alexsomesan]

Hi!
What specifically in the metadata does not get updated as you would expect?

[alexsomesan]

Might be actually improved by this change: #1097