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
I'm getting the following error:│ Warning: Failed to decode resource from state│ │ Error decoding "module.aml.azurerm_machine_learning_workspace.main" from prior state: unsupported attribute "managed_network"I haven't set`managed_network`, and in the docs it is flagged as optional.
Also, this resource has existed for a while now, and previous runs today were successful.
We changed nothing regarding the AML resources, but randomly got the this error.
Expected Behaviour
managed_network is optional, so it should not be necessary to set.
Although, it is currently not possible to set it because when I do TF complains that it's not expected. (see screenshot)
Actual Behaviour
Provisioning fails, and TF complains that managed_network is unsupported.
Steps to Reproduce
terraform plan
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
Hi @fschlz thanks for opening this issue. However, I am not able to reproduce the issue using AzureRM Provider Version 3.99.0 and the TF config below. Could you please provide a minimal reproducible TF config and repro steps to help reproduce/troubleshoot?
Is there an existing issue for this?
Community Note
Terraform Version
1.8.2
AzureRM Provider Version
3.100.0
Affected Resource(s)/Data Source(s)
azurerm_machine_learning_workspace
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
managed_network
is optional, so it should not be necessary to set.Although, it is currently not possible to set it because when I do TF complains that it's not expected. (see screenshot)
Actual Behaviour
Provisioning fails, and TF complains that
managed_network
is unsupported.Steps to Reproduce
terraform plan
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: