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
Error: Provider produced inconsistent result after apply
│
│ When applying changes to
│ module.apcfg_kv_db.azurerm_role_assignment.appgw_role[0], provider
│ "module.apcfg_kv_db.provider["registry.terraform.io/hashicorp/azurerm"]"
│ produced an unexpected new value: Root resource was present, but now
│ absent.
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
The text was updated successfully, but these errors were encountered:
I believe this is a duplicate of #12057, at least six issues covering this issue are opened the last few days. The PR fixing this problem is under review.
Most information how to solve it can be found under #12060
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Team,
My transformer pipeline is failing while creating role assignment to a managed identity which was working fine till azurerm provider 2.61
After upgrading to azurerm provider 2.62 I'm facing this issue.
Let me know if any additional info needed (screenshot attached
)
resource "azurerm_role_assignment" "appgw_role" {
depends_on = [azurerm_user_assigned_identity.appgw_identity]
scope = azurerm_user_assigned_identity.appgw_identity[0].id
role_definition_name = "Managed Identity Operator"
principal_id = data.azuread_service_principal.aks_obj_identity.object_id
}
Error message
Error: Provider produced inconsistent result after apply
│
│ When applying changes to
│ module.apcfg_kv_db.azurerm_role_assignment.appgw_role[0], provider
│ "module.apcfg_kv_db.provider["registry.terraform.io/hashicorp/azurerm"]"
│ produced an unexpected new value: Root resource was present, but now
│ absent.
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
The text was updated successfully, but these errors were encountered: