-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suppress metadata changes at terraform plan? #1315
Comments
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. |
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. |
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
|
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 Shows that some values that were set using |
Apologies, @BenB196 is correct, I was mistaken as we do not use It would be useful to have a |
Older helm provider versions didn't show this
metadata
changes when terraform detected a change/run plan, and the new helm provider versions are posting a wall of text ofmetadata
changes which have no real value (to me) and just clog up my tf plan output.example doing a tf plan on a helm resource where we only updated the image tag var:
let's say we only have a field
deploymentTimestamp
updated. We'd rather see the changed field only on terraform plan, and suppress the wholemetadata
update, e.g. terraform plan should only showThis way the terraform plan is clear and concise, more human (easier to read/follow) without the metadata removal. Does it make sense?
Terraform version, Kubernetes provider version and Kubernetes version
Terraform configuration
Question
Is there any way to suppress the
metadata
changes at terraform plan?The text was updated successfully, but these errors were encountered: