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
Occasionally workspace deployment fails with "unexpected new value: Root resource was present, but now absent":
action": "install",
"message": "de2ecc1f-b993-458c-bc38-39b431961773: Error message: \u001b[31m╷\u001b[0m\u001b[0m \u001b[31m│\u001b[0m \u001b[0m\u001b[1m\u001b[31mError: \u001b[0m\u001b[0m\u001b[1mProvider produced inconsistent result after apply\u001b[0m \u001b[31m│\u001b[0m \u001b[0m \u001b[31m│\u001b[0m \u001b[0m\u001b[0mWhen applying changes to \u001b[31m│\u001b[0m \u001b[0mmodule.azure_monitor.azurerm_monitor_private_link_scope.workspace, provider \u001b[31m│\u001b[0m \u001b[0m\"provider[\\\"registry.terraform.io/hashicorp/azurerm\\\"]\" produced an \u001b[31m│\u001b[0m \u001b[0munexpected new value: Root resource was present, but now absent. \u001b[31m│\u001b[0m \u001b[0m \u001b[31m│\u001b[0m \u001b[0mThis is a bug in the provider, which should be reported in the provider's \u001b[31m│\u001b[0m \u001b[0mown issue tracker
A workaround is to use the AzAPI provider, as per PR #3581
This needs further investigation and an issue creating in the Terraform provider repository.
The text was updated successfully, but these errors were encountered:
marrobi
changed the title
Workspace deployment fails with pp Insights Private Link Faliure
Workspace deployment fails with App Insights Private Link Faliure
Jul 20, 2023
SvenAelterman
changed the title
Workspace deployment fails with App Insights Private Link Faliure
Workspace deployment fails with App Insights Private Link Failure
Aug 24, 2023
Occasionally workspace deployment fails with "unexpected new value: Root resource was present, but now absent":
A workaround is to use the AzAPI provider, as per PR #3581
This needs further investigation and an issue creating in the Terraform provider repository.
The text was updated successfully, but these errors were encountered: