-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
azurerm_key_vault_certificate
- support for speciying the subject_alternative_name
#479
Comments
+1 on the above. |
azurerm_key_vault_certificate
- support for speciying the subject_alternative_name
Due to hacktober I decided to try my hand at this. The PR I submitted should fix this. @kevinneufeld: The thumbprint is already exported from what I can see. It was added in PR #1904 |
hi @jameswhinn @kevinneufeld @draggeta Just to let you know that this has been released as a part of v1.18 of the AzureRM Provider (the full changelog is available here). You can upgrade to this by specifying the version in the provider block (as shown below) and then running
Thanks! |
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! |
Currently the "azurerm_key_vault_certificate" resource does not allow for the creation of a SubjectAlternativeName within the X509CertificateProperties object. It would be great if the resource could be extended to allow for this.
The text was updated successfully, but these errors were encountered: