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

google_compute_ssl_certificate: mark private_key as sensitive #220

Merged
merged 1 commit into from
Jul 24, 2017

Conversation

renchap
Copy link
Contributor

@renchap renchap commented Jul 19, 2017

This prevents the private key to be displayed in terraform plan and terraform apply.
It does not impact anything else.

I considered marking certificate sensitive as well to avoid displaying a full certificate (+ intermediates) as it clutters the output and does not bring very readable information, but as it is not really sensitive data I did not do it. Feel free to tell me if you think this is a good idea.

@selmanj
Copy link
Contributor

selmanj commented Jul 24, 2017

Thanks for this change! I'm not eager to suppress certificate as sensitive just because it's verbose, but this private key labeling is absolutely correct.

@selmanj selmanj merged commit 15ddd67 into hashicorp:master Jul 24, 2017
@renchap renchap deleted the ssl_certificate_sensitive branch July 25, 2017 06:41
negz pushed a commit to negz/terraform-provider-google that referenced this pull request Oct 17, 2017
luis-silva pushed a commit to luis-silva/terraform-provider-google that referenced this pull request May 21, 2019
<!-- This change is generated by MagicModules. -->
/cc @danawillow
@ghost
Copy link

ghost commented Mar 31, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants