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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
The azurerm_nginx_certificate resource requires a key_vault_secret_id. Azure has deprecated the support for storing TLS certificates as a Key Vault Secret as there is now a dedicated Key Vault Certificate object.
The Azure NGINXaaS implementation has been updated to require Azure Key Vault Certificates but this provider's azurerm_nginx_certificate module has not. This breaks the ability to deploy NGINXaaS with a certificate using this provider.
Thanks for raising this issue. I see that there is slight confusion in how a certificate gets used in NGINXaaS for Azure. We allow users to reference a certificate object in the argument key_vault_secret_id. Can you please try the following example:
The example shows you that a deployment is referencing the secret ID of the corresponding certificate object. Please reach out if you see any issues in running the above example.
Is there an existing issue for this?
Community Note
Description
The azurerm_nginx_certificate resource requires a
key_vault_secret_id
. Azure has deprecated the support for storing TLS certificates as a Key VaultSecret
as there is now a dedicated Key VaultCertificate
object.The Azure NGINXaaS implementation has been updated to require Azure Key Vault Certificates but this provider's
azurerm_nginx_certificate
module has not. This breaks the ability to deploy NGINXaaS with a certificate using this provider.New or Affected Resource(s)/Data Source(s)
azurerm_nginx_certificate
Potential Terraform Configuration
References
No response
The text was updated successfully, but these errors were encountered: