az storage blob metadata update -> lease-id parameter removed in 2.38

[vincent-aviva]

This is autogenerated. Please review and update as needed.

Describe the bug

After acquiring a lease through "az storage blob lease acquire --proposed-lease-id " we would like to update the metadata on that blob. Untill 2.37 we could provide --lease-id to the command and then it should work.
However, in 2.38 this parameter is removed and if you remove it in the call then you get the response

There is currently a lease on the blob and no lease ID was specified in the request.
ErrorCode:LeaseIdMissing

Command Name
az storage blob metadata update

Errors:

unrecognized arguments: --lease-id 952eea37-83c3-4c34-a975-460eff59eae6

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

• `az storage blob lease acquire --account-name {} --subscription {} --auth-mode {} --container-name {} --blob-name {} --lease-duration {} --proposed-lease-id {}
• az storage blob metadata update --account-name {} --subscription {} --auth-mode {} --container-name {} --name {} --metadata {} {} --lease-id {} --output {} --verbose

Expected Behavior

The metadata of the blob is updated.

Environment Summary

Windows-10-10.0.22000-SP0
Python 3.10.5
Installer: MSI

azure-cli 2.38.0

Extensions:
azure-devops 0.25.0

Dependencies:
msal 1.18.0b1
azure-mgmt-resource 21.1.0b1

Additional Context

[yonzhan]

storage

[timkowal]

Seeing the same.

Code that worked two days ago now produces error message:

ERROR: unrecognized arguments: --lease-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

And the documentation page no longer lists the "--lease-id" parameter.

Previous page (courtesy of the Wayback Machine):

[olehb]

Any update on this regression issue?

[evelyn-ys]

@bebound Can you check if this is caused by track2 migration?