v3.0.0 - Use dynamic type for Helm chart values

[stevehipwell]

Description

Given that this provider can now support dynamic types and the fact that any object type is valid for the Helm values, it would make sense to make use of dynamic types when specifying chart values. This should be relevant to the set inputs, but would be even more powerful for the values input. The primary driver here is using the provider like Helm and passing in a block of YAML (or HCL) and getting a better diff on the changes.

Our current pattern is as follows and it results in a poor diff experience as the whole values string is shown for any change.

locals {
  chart_values = {
    myValue = "a"

    myOtherValue = {
      nestedValue = [1, 2, 3]
    }
  }
}

resource "helm_release" "test" { 
  values = [yamlencode(local.chart_values)]
}

If the values type was made dynamic it could support list of strings, a single string, list of object, or object; and the diff would only show the actual changes instead of the whole string.

Potential Terraform Configuration

The example from above could then be represented by the following code.

locals {
  chart_values = {
    myValue = "a"

    myOtherValue = {
      nestedValue = [1, 2, 3]
    }
  }
}

resource "helm_release" "test" { 
  values = local.chart_values
}

References

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