Skip to content
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

scaleway_lb_certificate.custom_certificate.certificate_chain is not marked as sensitive #2761

Closed
jlaine opened this issue Oct 3, 2024 · 0 comments · Fixed by #2771
Closed
Assignees
Labels
load-balancer Load-balancer issues, bugs and feature requests

Comments

@jlaine
Copy link

jlaine commented Oct 3, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v1.9.6
on linux_amd64

  • provider registry.terraform.io/hashicorp/random v3.6.3
  • provider registry.terraform.io/scaleway/scaleway v2.46.0

Expected Behavior

The certificate_chain contains the private key for the TLS certificate, and as such is sensitive information. I would expect it to be marked as sensitive in the schema.

Actual Behavior

As far as I can tell this field is not marked as sensitive:

"certificate_chain": {
Type: schema.TypeString,
Required: true,
ForceNew: true,
Description: "The full PEM-formatted certificate chain",
},

@jremy42 jremy42 added the load-balancer Load-balancer issues, bugs and feature requests label Oct 4, 2024
@yfodil yfodil linked a pull request Oct 11, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
load-balancer Load-balancer issues, bugs and feature requests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants