Improve metadata attribute by adding last deployed date

[danielskowronski]

Description

helm_release has an attribute metadata that's missing "last updated" date which is always returned by Helm. That field (combined with app_revision) is quite useful to determine triggers in complex deployment scenarios, as it's the closest thing to a release UUID we have.

Potential Terraform Configuration

This is example code that implements a crude workaround that's not 100% bullet-proof (and probably violates many Terraform usage guides, but it's only an example). Availability of helm_release.foo.metadata.last_deployed would make this example trick with description obsolete.

resource "helm_release" "foo" {
  name        = "foo"
  repository  = "./foo/"
  wait        = true
  description = "foo planned at ${timestamp()}"

  lifecycle {
    ignore_changes = [
      description
    ]
  }
}

resource "helm_release" "bar" {
  name        = "bar"
  repository  = "./bar/"
  wait        = true
  description = "bar planned at ${timestamp()}"

  depends_on = [
    helm_release.foo
  ]

  lifecycle {
    replace_triggered_by = [
      helm_release.foo.metadata.revision,
      helm_release.foo.description,
    ]
    ignore_changes = [
      description
    ]
  }
}

References

• in my original work I was attempting to mitigate the consequences of Helm post-install hooks are not triggered when used by helm_release and wait = true #683 by adding "validator" chart; however, that's irrelevant to this feature request
• https://helm.sh/docs/helm/helm_status/#synopsis

example execution helm get all foo showing what's available (descriptions managed by example trick from above):

NAME: foo
LAST DEPLOYED: Tue May 28 17:31:40 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
CHART: foo
VERSION: v0.0.2
APP_VERSION: 
TEST SUITE: None
USER-SUPPLIED VALUES:
description: foo planned at 2024-05-28T15:29:53Z

COMPUTED VALUES:
description: foo planned at 2024-05-28T15:29:53Z
key1: value1

HOOKS:
MANIFEST:
...

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

[danielskowronski]

Resolved by #1380 :)