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

Expose tls_private_key PEM also in PKCS#8 (RFC 5208) format #210

Closed
1 task done
detro opened this issue May 11, 2022 · 5 comments · Fixed by #225
Closed
1 task done

Expose tls_private_key PEM also in PKCS#8 (RFC 5208) format #210

detro opened this issue May 11, 2022 · 5 comments · Fixed by #225
Assignees
Milestone

Comments

@detro
Copy link
Contributor

detro commented May 11, 2022

Terraform CLI and Provider Versions

0.12

Use Cases or Problem Statement

In the current implementation of this provider, it's possible to provide Private Key PEMs in PKCS#8 format to certificate resources and data sources. Yet, is not possible to use tls_private_key to get the key in PEM PKCS#8 format.

To be exact, we can get it only for tls_private_key created with algorithm = ED25519, as that's the only format Go crypto libraries support for it.

Proposal

Add a .private_key_pem_pkcs8 field to tls_private_key resource.

How much impact is this issue causing?

Low

Additional Information

This missing feature was spotted here.

Related #91
Related #55

Code of Conduct

  • I agree to follow this project's Code of Conduct
@detro detro added this to the next.major milestone May 11, 2022
@detro detro modified the milestones: next.major, next.major.framework-port May 16, 2022
@nikodemjedynak-dnv
Copy link

Any updates?

@detro
Copy link
Contributor Author

detro commented Jun 27, 2022

incoming

@wasfree
Copy link

wasfree commented Jul 18, 2022

Would be cool to have this feature available soon in 4.0

@detro
Copy link
Contributor Author

detro commented Jul 21, 2022

Hey @wasfree - thanks for your message.
We are working on it as we speak: a few kinks to iron out.

Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants