-
Notifications
You must be signed in to change notification settings - Fork 103
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
Add PKCS12 archive bundle to self-signed certificate resource #69
Conversation
@appilon, @julienduchesne any chance this gets reviewed in the next days? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tested this PR on my side and had to make 2 changes to get it running.
|
Hi guys any update on this? |
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
This would be a massive feature for us as we use Azure and they almost universally expect certificates in the pfx format. Currently we do lots and lots of workarounds with local-exec and external provider to manage this. Would really like to see this feature added. PFX support is crucial as it is the main type of certificate in the Microsoft ecosystem (for better or worse). |
Superseded by #205. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Resolves #29