-
Notifications
You must be signed in to change notification settings - Fork 377
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
helm_release does not respect sensitive
attribute anymore
#1221
Comments
Hi @audunsolemdal, Thank you for raising this question. It looks like it happens due the properties of the I would advise using the resource "helm_release" "sentry" {
...
set_sensitive {
name = "mail.password"
value = var.sendgrid_apikey
}
} |
just to hopefully get more visibility, (or any workarounds) there is still an edgecase where if the name contains a "." there is currently no way to hide the sensitive values in the metadata. this pr contains an example of this |
@arybolovlev Can't agree with this kind of approach. You cannot introduce severe security issue and respond with "use this solution" instead. Wondering why the output hides sensitive data correctly on |
Marking this issue as stale due to inactivity. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. This helps our maintainers find and focus on the active issues. Maintainers may also remove the stale label at their discretion. Thank you! |
comment for activity |
I'm having an issue with sensitive values outputting into the plan when I use the resource "helm_release" "my_helm" {
name = "my-helm"
repository = local.repo
chart = "my-chart"
version = "0.1.0"
namespace = "default"
values = [
templatefile("values/my-helm/values.tpl.yml", {
PASSWORD = sensitive(data.sops_file.my_helm.data["password"])
})
]
} resource "helm_release" "my_helm" {
name = "my-helm"
repository = local.repo
chart = "my-chart"
version = "0.1.0"
namespace = "default"
values = [
sensitive(templatefile("values/my-helm/values.tpl.yml", {
PASSWORD = data.sops_file.my_helm.data["password"]
}))
]
}
|
Terraform, Provider, Kubernetes and Helm Versions
Affected Resource(s)
Terraform Configuration Files
relevant part of templates/values.yaml.tpl
Debug Output
https://gist.github.com/audunsolemdal/b61129ae5a54dc8a9c23cb47f3d6c7c8
I believe this problem was added through in #1097 prior to that I do not recall this happening.
Steps to Reproduce
terraform apply
Expected Behavior
sensitive attributes should stay hidden
Actual Behavior
sensitive attributes are displayed in clear text
References
Community Note
The text was updated successfully, but these errors were encountered: