Terraform-provider-helm: Updating just the chart version doesn't trigger an update in terraform

[aaronmell]

I'm bumping the version of the chart in a chartmuseum repo, however when I run apply in terraform, I get no changes.

The change I made to the chart, was I added an annotation to a pod.

[robinkb]

Can you share how you defined your helm_release resource?
Changing the chart version of a release correctly triggers an update for me.

[aaronmell]

resource "helm_release" "release_name" {
name = "release_name"
repository = "${var.helm_repository_name}"
chart = "chartrepo/chart_name"
namespace = "${var.release_namespace_name}"
depends_on = ["null_resource.dependency"]

values = [
"${file("path_to_config")}"
]

After that we have a bunch of sets. This happened twice on my local
machine, but I couldn't reproduce in our prod environment

On Thu, Aug 9, 2018 at 5:58 AM robinkb [e-mail] wrote:

Can you share how you defined your helm_release resource?
Changing the chart version of a release correctly triggers an update for
me.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mcuadros/terraform-provider-helm/issues/102#issuecomment-411719569,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAd8zsi49f8XpnClBdwjwUWldeRdHtOOks5uPBXZgaJpZM4VzBO9
.

[sebastien-prudhomme]

Same thing here: updating a chart version in the chart repository doesn't trigger an update when using an helm_release that doesn't set a specific version.

If i read the doc, it's not clear if the latest version is just used when installing and upgrading or just when installing:

version - (Optional) Specify the exact chart version to install. If this is not specified, the latest version is installed.

[abulfatmasimov]

bump, same here :(

[aaronmell]

I traced through the code, and I understand what the issue is. I don't know any GO so I'm not sure I could stumble through things and fix it.

The issue is that when resourceReleaseRead is called it never checks with helm to see what version charts exist. If you force specify a version of your chart, that works, because changing the value forces an update.

Probably needs a bit of thought put behind it, and a way to configure the semantic versioning you are willing to take.

[abulfatmasimov]

Thank you @aaronmell for taking time looking into this.
So if I understand it correctly, doc is a bit misleading when saying it would install the latest since it does not check what the latest version is:

version - (Optional) Specify the exact chart version to install. If this is not specified, the latest version is installed.

This seems like a bug to me.

[dev-e]

As a workaround I suggest to make simply this:

resource "null_resource" "helm_update" {
  triggers = {
    always_run = "${timestamp()}"
  }

  provisioner "local-exec" {
    command = "helm update"
  }
}

[ichekrygin]

Is there any way to bump the priority on this?
It renders helm_release unusable w/out version flag.
The @dev-e workaround ^ doesn't fix the issue.

provisioner "local-exec" {
    command = "helm update; helm search my-repo/my-chart"
}

^ shows correct new chart version, and yet helm_release update is not triggered.

[hashibot]

This issue has been open 180 days with no activity. If this issue is reproducible with the latest version of the provider and with Terraform 0.12, please comment. Otherwise this issue will be closed in 30 days.

[aareet]

This is the expected behaviour - we want to encourage the practice of being explicit about the upgrade version when upgrading an installed chart. We'll take a note to improve the documentation referenced above.

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!