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
hmrc87
changed the title
subnet_resource_id should be optional, even though node_public_ip_enabled is false
azurerm_machine_learning_compute_cluster subnet_resource_id should be optional, even though node_public_ip_enabled is false
May 8, 2024
However in a private networking scenario with a managed net I can setup a compute without public ip and without an explicit subnetid via the azure ui as described above.
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.8.2
AzureRM Provider Version
3.98.0
Affected Resource(s)/Data Source(s)
azurerm_machine_learning_compute_cluster
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Since we are in a private networking scenario with a Managed VNET I don't have to provide the subnetid in the Azure MLW UI.
I have created a compute cluster manually in my scenario via Azure UI and it says subnetid NULL and "enableNodePublicIp": false
Actual Behaviour
Error:
subnet_resource_id
must be set ifnode_public_ip_enabled
is set tofalse
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: