-
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
Gracefully degrade "List Account Keys" during plan phase #4138
Comments
…e user doesn't have permissions When the user doesn't have permissions to access the ListKeys endpoint, either because the Resource has a Write Lock (where ListKeys counts as a Write Operation, which is being tracked in Azure/azure-rest-api-specs#6363) or because the user doesn't have permissions - this now degrades these fields into empty values, rather than outright failing. fixes #4138
This has been released in version 1.34.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.34.0"
}
# ... other configuration ... |
@tombuildsstuff provider "azurerm" {
version = "~> 1.34.0" Log:
|
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! |
Community Note
Description
Currently when running plan if the user does not have access to
listKeys
on the storage account resource the plan phase will fail. As mentioned in #3651 it could be totally fine, and intentional (least privilege), for the user running plan to not require this access. It would be good if the plan phase could gracefully degrade, perhaps returning empty strings, if the user doesn't have permission tolistKeys
.New or Affected Resource(s)
References
The text was updated successfully, but these errors were encountered: