Suppress metadata changes at terraform plan? about terraform-provider-helm

[eklesel]

Would also be very interested in this, we have a fairly hefty internal helm chart with a few dependencies and a large values input spread across multiple files. When a single values file is updated (even just adding a space), the entire metadata is recomputed and showing as changed, although the value is not known as it's computed.

From a recent plan, the metadata takes up 2183 lines of a total 2392, we're currently forced to redirect stdout of apply/plan runs to a text to then read the plan, and in CI it causes huge job logs which is completely unnecessary.

For us, the metadata of the helm chart is useless and we'd like to disable the computation if possible (or at least hide it from output).

We already mark the values file as sensitive because the output is similarly huge, it outputs the entire text file before/after instead of just showing the values which have changed/added/removed. For large values files this is useless for comparison, so we compare changes using the manifest experiment instead which works very well.

[MiguelNdeCarvalho]

I'm really curious if this is possible to do, as I'm using the https://registry.terraform.io/providers/hashicorp/helm/latest/docs#manifest experiment.

[sbeginCoveo]

We're in the same situation, we managed to silence the values diff, but now were back at square one with a huge and useless diff in our terraform plans

      ~ values                     = (sensitive value)

[eklesel]

Another point which is probably of more serious concern, the metatadata output will show sensitive values.

When changing any values in the helm_release resource the entire metadata output is shown, even if sensitive values aren't changed.

[BenB196]

Another point which is probably of more serious concern, the metatadata output will show sensitive values.

When changing any values in the helm_release resource the entire metadata output is shown, even if sensitive values aren't changed.

I don't believe this is (at least 100%) accurate, at least on the latest version 2.12.1.

Shows that some values that were set using set_sensitive are being properly hidden

[eklesel]

Apologies, @BenB196 is correct, I was mistaken as we do not use set_sensitive to set sensitive variables, therefore they're displayed.

It would be useful to have a values_sensitive parameter so that we can set sensitive values using freeform YAML, but that's another issue.