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
Problem Description
Documentation of the Data Source azurerm_key_vault_secret is still mentioning the "vault_uri" property. This property has been deprecated in favour of "key_vault_id".
Please update the documentation accordingly ("argument reference" and "example usage").
For the sake of completeness: This issue has been raised before.
The text was updated successfully, but these errors were encountered:
This resolves#3162.
Updated "vault_uri" to "key_vault_id" for data.azurerm_key_vault_secret since "vault_uri" has been deprecated in favor of "key_vault_id".
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!
ghost
locked and limited conversation to collaborators
May 13, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Problem Description
Documentation of the Data Source
azurerm_key_vault_secret
is still mentioning the "vault_uri" property. This property has been deprecated in favour of "key_vault_id".Please update the documentation accordingly ("argument reference" and "example usage").
For the sake of completeness: This issue has been raised before.
The text was updated successfully, but these errors were encountered: