-
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 Thumbprint output not accepted #2361
Comments
hi @iharrington Thanks for opening this issue :) So that we could take a look into this - would it be possible to post which version of the AzureRM Provider you're using? You can find this out by running Thanks! |
@tombuildsstuff This is in the .terraform plugin folder |
@tombuildsstuff Sorry to bug you, is anyone looking into this? |
This has been released in version 2.13.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 = "~> 2.13.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 👉 [email protected]. Thanks! |
Community Note
Terraform (and AzureRM Provider) Version
Terraform v0.11.10
Affected Resource(s)
Terraform Configuration Files
I'm using test code from your docs "Example Usage (Generating a new certificate)"
Expected Behavior
thumbprint - The X509 Thumbprint of the Key Vault Certificate returned as hex string.
Should be available attribute
Actual Behavior
'Unresolved resource' via HCL plugin.
Steps to Reproduce
Important Factoids
I'm using IntelliJ IDEA (version 2018.2.6 CE) w/ HashiCorp Terraform /HCL Languag Support (Version: 0.6.12)
References
Terraform docs
Closed issue
The text was updated successfully, but these errors were encountered: