Proposal: New data source for TLS cert

[hashibot]

This issue was originally opened by @martinssipenko as hashicorp/terraform#14856. It was migrated here as part of the provider split. The original body of the issue is below.

---

I would like to propose a new data source under TLS provider named tls_cert (or something like that).

Arguments:

• You would be able to either supply a path to TLS certificate as argument, or supply a PEM, which could be read by ${file('path/to/cert.pem')}.

Attributes:

• signature_algo
• public_key_algo
• serial_number (represented as integer)
• serial_number_hex (represented as hex delimited with :)
• is_ca
• version
• issuer
• subject
• not_before
• not_after

Possibly even more.

Please share your view on introducing such provider.

[apparentlymart]

Hi @martinssipenko! Thanks for this suggestion and sorry for the long silence here.

Supporting such a data source seems like a fine idea, and I think it could share a lot of the existing certificate resource implementation to achieve its goal.

It's unlikely that the Terraform team at HashiCorp will be able to work on this in the near future due to being busy with other work, but we'd be happy to review a pull request for this if someone else has the time and motivation to work on it.

[FrenchBen]

Since I did something similar for the Private key -> Public key, I'll see if I can find time to work on datasource for this.

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.