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.
The managed_disk block wants to replace the disks, the network_interface block wants to replace networking and it wants to add the unmanaged_disk block which will force replacement even though we are only using managed disks
Steps to Reproduce
Pin provider to version 3.114.0
terraform init
terraform plan
Reverting to the previous provider version 3.113.0 avoids the drifts/destruction
Hi @rcskosir we have updated to the latest version of the azurerm provider major release 4.0.1 and we still have this issue. May you please provide us any insight on how we can get this fixed? Thanks
👋 @enorlando Thanks for reaching out, unfortunately I do not have an ETA on this bug. Any future work via the team or the community should end up linked here via a PR.
@jackofallops Do you see any reason why we are coming up with this behaviour? It seems to have started after the PR #26822 was merged as part of v3.14.0 milestone. Reverting back to the previous version removes the behaviour. We are currently using v4.0.1 of the provider and still experiencing the same. Removing from state and importing still has the same issue.
Is there an existing issue for this?
Community Note
Terraform Version
1.9.3
AzureRM Provider Version
3.114.0
Affected Resource(s)/Data Source(s)
azurerm_site_recovery_replicated_vm
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
No changes. Infrastructure is up to date
Actual Behaviour
The
managed_disk
block wants to replace the disks, thenetwork_interface
block wants to replace networking and it wants to add theunmanaged_disk
block which will force replacement even though we are only using managed disksSteps to Reproduce
Reverting to the previous provider version 3.113.0 avoids the drifts/destruction
Important Factoids
No response
References
#26822
The text was updated successfully, but these errors were encountered: