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
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the
│ plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.
Steps to Reproduce
terraform apply
Important Factoids
No response
References
I thought #21110 and #21311 would fix it but I'm still having issues on the latest version. This was previously raised under #21277
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is there an existing issue for this?
Community Note
Terraform Version
1.4.4
AzureRM Provider Version
3.51.0
Affected Resource(s)/Data Source(s)
azurerm_automation_software_update_configuration
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
automation-accounts["main"].azurerm_automation_software_update_configuration.main["auto"] will be created
automation_account_id = ""
duration = "PT3H0M0S"
error_code = (known after apply)
error_meesage = (known after apply)
error_message = (known after apply)
id = (known after apply)
name = "auto"
operating_system = "Windows"
schedule {
}
target {
locations = []
scope = []
tag_filter = (known after apply)
tags {
]
}
}
}
windows {
]
}
}
Actual Behaviour
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the
│ plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.
Steps to Reproduce
terraform apply
Important Factoids
No response
References
I thought #21110 and #21311 would fix it but I'm still having issues on the latest version. This was previously raised under #21277
The text was updated successfully, but these errors were encountered: