Azure Machine Learning container registry cannot be changed due to the lack of "--yes" argument

[BzSpi]

Describe the bug When trying to update a Machine Learning Workspace container registry, I have the following message:

# $ az ml workspace update -n xxxxxx -g xxxxxx --container-registry /subscriptions/xxxxxx/resourceGroups/xxxxxx/providers/Microsoft.ContainerRegistry/registries/xxxxxx
Command group 'ml workspace' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
Updating the workspace-attached Azure Container Registry resource may break lineage of previous jobs or your ability to rerun earlier jobs in this workspace. Are you sure you want to perform this operation? Include the --yes parameter with this request to confirm.

And when I use the same command with the --yes flag, Azuz CLI yields that argument is not recognized

# $ az ml workspace update -n xxxxxx -g xxxxxx --container-registry /subscriptions/xxxxxx/resourceGroups/xxxxxx/providers/Microsoft.ContainerRegistry/registries/xxxxxx --yes
unrecognized arguments: --yes

To Reproduce Use the commands above.

Expected behavior It updates the machine learning workspace associated registry.

Environment summary

Additional context I use the v2 extension.

[yonzhan]

route to CXP team

[chriswue]

Is there a work-around? The CR cannot be changed via Azure Portal and the CLI is broken. We're now stuck with a more-or-less unusable workspace.

[SatishBoddu-MSFT]

Hello @BzSpi @chriswue

Thank you for reporting this issue, we are routing this to service Teams' attention!

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureml-github.

Issue Details

---

Describe the bug When trying to update a Machine Learning Workspace container registry, I have the following message:

# $ az ml workspace update -n xxxxxx -g xxxxxx --container-registry /subscriptions/xxxxxx/resourceGroups/xxxxxx/providers/Microsoft.ContainerRegistry/registries/xxxxxx
Command group 'ml workspace' is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
Updating the workspace-attached Azure Container Registry resource may break lineage of previous jobs or your ability to rerun earlier jobs in this workspace. Are you sure you want to perform this operation? Include the --yes parameter with this request to confirm.

And when I use the same command with the --yes flag, Azuz CLI yields that argument is not recognized

# $ az ml workspace update -n xxxxxx -g xxxxxx --container-registry /subscriptions/xxxxxx/resourceGroups/xxxxxx/providers/Microsoft.ContainerRegistry/registries/xxxxxx --yes
unrecognized arguments: --yes

To Reproduce Use the commands above.

Expected behavior It updates the machine learning workspace associated registry.

Environment summary

Additional context I use the v2 extension.

Author:	BzSpi
Assignees:	-
Labels:	Service Attention, Machine Learning, customer-reported, Auto-Assign
Milestone:	Backlog

[luigiw]

@SatishBoddu-MSFT please confirm if this is still an active issue.

[ghost]

Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

[BzSpi]

Do not close

[needuv]

@mingweihe could you please take a look at this issue?

[mingweihe]

Hi @BzSpi , happy new year, thanks for the request.

The argument has been changed. Please update the CLI version by following the guides on this page: https://learn.microsoft.com/en-us/azure/machine-learning/how-to-configure-cli?tabs=public

Then use the new argument -u/--update-dependent-resources instead. https://learn.microsoft.com/en-us/cli/azure/ml/workspace?view=azure-cli-latest#az-ml-workspace-update

A full command line could be

az ml workspace update -g <resource group name> -n <workspace name> --container-registry <ACR arm ID> -u

[ggirard07]

Last time I tried the -u option (v2.5.0), the update was still being refused and I had to "manually" invoke the PATCH request myself instead with Postman (sorry I do not have a workspace available to test it again on)

[mingweihe]

Hi @ggirard07 , please try to use the latest version: 2.11.0

[MatthewHessCygrp]

I want to write and confirm that I DID get this to work with azure-cli 2.53.1 and ml 2.21.1

Here is the command that worked:

az ml workspace update -n {workspace name} -g {resource group name} --container-registry {NEW registry ID} -u

Note that the {NEW registry ID} is the full path such as:

container-registry/subscriptions/{subscriptionID}/resourceGroups/{resourcegroupID}/providers/Microsoft.ContainerRegistry/registries/{registryID}

[snacks-lord]

I want to make this change, but I want to know if this will change anything on the workspace (will anything be deleted?) I can't find an answer to this question anywhere.

[sharmuz]

I want to write and confirm that I DID get this to work with azure-cli 2.53.1 and ml 2.21.1

Here is the command that worked:

az ml workspace update -n {workspace name} -g {resource group name} --container-registry {NEW registry ID} -u

Note that the {NEW registry ID} is the full path such as:

container-registry/subscriptions/{subscriptionID}/resourceGroups/{resourcegroupID}/providers/Microsoft.ContainerRegistry/registries/{registryID}

This worked for me, except that for {NEW registry ID} I had to omit the prefix "container-registry". I.e:

/subscriptions/{subscriptionID}/resourceGroups/{resourcegroupID}/providers/Microsoft.ContainerRegistry/registries/{registryID}

For those unaware, you can easily grab this from the Azure portal page for your Azure ML workspace. On the Overview page click "JSON view" in the top right - you'll see the key "id" at the top, copy the associated value.