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 comments along the lines of "+1", "me too" or "any updates", 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 and review the contribution guide to help.
│ Error: Provider produced inconsistent result after apply
│ When applying changes to
│ module.azure_monitor_private_link_scope.azurerm_monitor_private_link_scope.ampls,
│ provider "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced
│ an unexpected new value: Root object was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's│ own issue tracker.
Expected Behaviour
No response
Actual Behaviour
No response
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
Hi @q-renjoseph, thanks for submitting this!
I cannot reproduce this in my local environment, this might be caused by unstable API. Could you please try it again with debug option and check the API flow if Azure API is returning unexpected 404 status code in GET operation after PUT.
Is there an existing issue for this?
Community Note
Terraform Version
1.9.0
AzureRM Provider Version
3.117.0
Affected Resource(s)/Data Source(s)
azurerm_monitor_private_link_scope
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
No response
Actual Behaviour
No response
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: