-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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] - switches the emails
, dns_names
, upns
of the subject_alternative_names
property to use TypeSet
#4645
Conversation
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.
Hi @hbuckle,
You are entirely correct these should be a set. However its not so easy to simply change the type. You are also going to need to update the flatten&expand functions to handle the fact its no longer an list:
Test ended in panic.
------- Stdout: -------
=== RUN TestAccAzureRMKeyVaultCertificate_basicGenerateSans
=== PAUSE TestAccAzureRMKeyVaultCertificate_basicGenerateSans
=== CONT TestAccAzureRMKeyVaultCertificate_basicGenerateSans
------- Stderr: -------
2019/10/18 13:45:19 [DEBUG] Registering Data Sources for "Compute"..
2019/10/18 13:45:19 [DEBUG] Registering Resources for "Compute"..
panic: interface conversion: interface {} is *schema.Set, not []interface {}
@katbyte yes of course, now updated |
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.
Thanks @hbuckle!
Tests pass and LGTM now 👍
emails
, dns_names
, upns
of the subject_alternative_names
property to use TypeSet
This has been released in version 1.36.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 1.36.0"
}
# ... other configuration ... |
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! |
I noticed when importing an existing certificate these properties did not come back in the same order as the configuration, so Terraform wanted to recreate the certificate.