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
No modification on the existing azurerm_virtual_desktop_workspace_application_group_association
Actual Behaviour
terraform apply cause virtual machine replacement but no modification in tf file. This problem appear in 0.35 and is still present in 0.37. When reverting to 0.34 no modification found when terraform plan/apply
Here is the plan output with 0.35+:
Terraform will perform the following actions:# module.azurerm_virtual_desktop_test.azurerm_virtual_desktop_application_group.appgroup will be updated in-place
~ resource"azurerm_virtual_desktop_application_group""appgroup" {
~ host_pool_id="/subscriptions/XXXXXXXXX-XXXX-XXXX-XXXX/resourceGroups/TEST-rg/providers/Microsoft.DesktopVirtualization/hostpools/SRVTEST-hp"->"/subscriptions/XXXXXXXXX-XXXX-XXXX-XXXX/resourcegroups/TEST-rg/providers/Microsoft.DesktopVirtualization/hostpools/SRVTEST-hp"id="/subscriptions/XXXXXXXXX-XXXX-XXXX-XXXX/resourcegroups/TEST-rg/providers/Microsoft.DesktopVirtualization/applicationgroups/SRVTEST-appgroup"location="eastus"name="SRVTEST-appgroup"resource_group_name="TEST-rg"tags={}
type="Desktop"
}
# module.azurerm_virtual_desktop_test.azurerm_virtual_desktop_workspace_application_group_association.workspaceremoteapp must be replaced-/+resource"azurerm_virtual_desktop_workspace_application_group_association""workspaceremoteapp" {
~ application_group_id="/subscriptions/XXXXXXXXX-XXXX-XXXX-XXXX/resourceGroups/TEST-rg/providers/Microsoft.DesktopVirtualization/applicationgroups/SRVTEST-appgroup"->"/subscriptions/XXXXXXXXX-XXXX-XXXX-XXXX/resourcegroups/TEST-rg/providers/Microsoft.DesktopVirtualization/applicationgroups/SRVTEST-appgroup"# forces replacement
~ id="/subscriptions/XXXXXXXXX-XXXX-XXXX-XXXX/resourcegroups/TEST-rg/providers/Microsoft.DesktopVirtualization/workspaces/SRVTEST-ws|/subscriptions/XXXXXXXXX-XXXX-XXXX-XXXX/resourcegroups/TEST-rg/providers/Microsoft.DesktopVirtualization/applicationgroups/SRVTEST-appgroup"-> (known after apply)
~ workspace_id="/subscriptions/XXXXXXXXX-XXXX-XXXX-XXXX/resourceGroups/TEST-rg/providers/Microsoft.DesktopVirtualization/workspaces/SRVTEST-ws"->"/subscriptions/XXXXXXXXX-XXXX-XXXX-XXXX/resourcegroups/TEST-rg/providers/Microsoft.DesktopVirtualization/workspaces/SRVTEST-ws"# forces replacement
}
Steps to Reproduce
Implement VDI hostpool and virtual machine. Use azurerm_virtual_desktop_workspace_application_group_association and update module to 035+
terraform plan
References
It seems there is pull request #9057 has been done on azurerm_virtual_desktop_workspace_application_group_association that can cause this issue
The text was updated successfully, but these errors were encountered:
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked as resolved and limited conversation to collaborators
Dec 27, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
Terraform version: 0.13.5
Provider AzureRM: v0.35+ (including latest v0.37)
Affected Resource(s)
virtual_desktop_workspace_application_group_association
Terraform Configuration Files
Expected Behaviour
No modification on the existing azurerm_virtual_desktop_workspace_application_group_association
Actual Behaviour
terraform apply cause virtual machine replacement but no modification in tf file. This problem appear in 0.35 and is still present in 0.37. When reverting to 0.34 no modification found when terraform plan/apply
Here is the plan output with 0.35+:
Steps to Reproduce
terraform plan
References
It seems there is pull request #9057 has been done on azurerm_virtual_desktop_workspace_application_group_association that can cause this issue
The text was updated successfully, but these errors were encountered: