You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, all 3 of these outputs really contain some kind of hash of the private key input, rather than the private key itself. This is consistent with the upstream Terraform documentation for e.g. tls_self_signed_cert:
Only an irreversable secure hash of the private key will be stored in the Terraform state.
I understand that the Pulumi docs are generated from the Terraform docs, but is there any way to override the documentation for these 3 fields to explain that the fields really contain a hash of the private key? Or to rename the fields privateKeyHash / caPrivateKeyHash, since they don't contain any PEM data?
@susanev Thanks for moving this issue over to pulumi-tls (and bringing it to our attention). We can't do anything about it right now, but this is an excellent test case for our "user edited docs" work stream.
The
SelfSignedCert.privateKeyPem
andCertRequest.privateKeyPem
outputs are both documented as:Similarly, the
LocallySignedCert.caPrivateKeyPem
output is documented as:However, all 3 of these outputs really contain some kind of hash of the private key input, rather than the private key itself. This is consistent with the upstream Terraform documentation for e.g. tls_self_signed_cert:
I understand that the Pulumi docs are generated from the Terraform docs, but is there any way to override the documentation for these 3 fields to explain that the fields really contain a hash of the private key? Or to rename the fields
privateKeyHash
/caPrivateKeyHash
, since they don't contain any PEM data?Reproduction:
After
pulumi up
, the outputs show that while the 2PrivateKey.privateKeyPem
outputs return a PEM-encoded certificate, the other 3 return hashes:The text was updated successfully, but these errors were encountered: