azure-cli 2.77.0: 'az batch application package create' does not upload zip package to blob

[tvn-mpm]

Describe the bug

Hello Azure CLI Team,

I'm reporting what appears to be a regression or a breaking change in the behavior of the az batch application package create command starting with azure-cli version 2.77.0.

Since updating to version 2.77.0, the exact same command does not upload the zip package to Azure Storage Account. The command does not end with an error but blob content contains just path to zip package used in --package-file parameter. This problem does not exist in version 2.76.0.

Steps to Reproduce:

1. Use azure-cli version 2.77.0.
2. Create an initial application package version
   az batch application package create --application-name $application_name --name $name --resource-group $group --version $application_version --package-file $package

Thank you for your help,
Tomas

Related command

az batch application package create --application-name $application_name --name $name --resource-group $group --version $application_version --package-file $package

Errors

No error returned by the command

Issue script & Debug output

az batch application package create --application-name $application_name --name $name --resource-group $group --version $application_version --package-file $package

Expected behavior

ZIP package is uploaded to blob in Azure Storage Account

Environment Summary

Azure CLI: 2.77.0

Additional context

No response

[yonzhan]

Thank you for opening this issue, we will look into it.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dpwatrous, @wiboris, @cRui861, @skapur12, @wanghoppe.

[manasmagdum]

Same issue for Azure functions as well.
#32044

Need quick resolution.

[pltaylor]

Just for short term fixability... if you run
'pip install azure-cli==2.76.0'
before the az cli command in a ADO classic pipeline using a hosted agent it will revert to the last version and address this issue.