Open enorlando opened 1 month ago
@rcskosir have you had a chance to review this issue we are currently experiencing with provider version 3.114.0?
@rcskosir any idea when we can get an update on this?
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
:wave: @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 https://github.com/hashicorp/terraform-provider-azurerm/pull/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
Important Factoids
No response
References
https://github.com/hashicorp/terraform-provider-azurerm/pull/26822