Closed lightdrive closed 4 days ago
With the latest v1.14.0
i am able to deploy all resources just fine, but on the project, every update causes the following validation error:
{
│ "error": {
│ "code": "ValidationError",
│ "severity": null,
│ "message": "Managed network cannot be disabled once enabled.",
│ "messageFormat": null,
│ "messageParameters": null,
│ "referenceCode": null,
│ "detailsUri": null,
│ "target": null,
│ "details": [],
│ "innerError": null,
│ "debugInfo": null,
│ "additionalInfo": null
│ },
...
│ }
My property bag does not include any managed vnet references:
...
body = {
kind = "Project"
properties = {
description = "AI Studio Project - ${var.ai_studio_project_name}"
friendlyName = title(replace(var.ai_studio_project_name, "-", " "))
hubResourceId = var.ai_studio_hub_id
}
}
...
Is anyone experiencing the same issues?
Hi @marvinbuss , would you please open another issue for your case? It seems unrelated with this one.
Hi @marvinbuss , would you please open another issue for your case? It seems unrelated with this one.
@ms-henglu: I just created another issue here: https://github.com/Azure/terraform-provider-azapi/issues/564
Hi @lightdrive ,
Thank you for taking time to report this issue.
Actually this resource type is supported by the latest azapi release, more details see: https://learn.microsoft.com/en-us/azure/templates/microsoft.machinelearningservices/2024-04-01/workspaces/connections?pivots=deployment-language-terraform
I'll close this issue as it's resolved, and feel free to reopen it if there's any questions.
Overview
Whilst we are waiting for a native resource or an update in the AzureRM provider to provision Azure AI Studio we are instead trying the Az API provider but the required version 2024-04-01 is not listed as supported. When will it be added and released?
Machine Learning Connections
Description
We've used Az API to provision almost all of the new resource types required for Azure AI Studio by using the newer API and setting __schema_validation__ to false apart from Machine Learning Connections, we can provision them but subsequent runs cause a provider crash on reading the resource.
Issue is similar to #502 but we have been able to add the location field to the resources and it still crashes on the read.
We are not expecting a bug fix here since we have bypassed the supported version.