az functionapp deployment source config-zip broken in 2.77.0

[Naktibalda]

Describe the bug

Since upgrade to 2.77.0 az functionapp deployment source config-zip -g $AZURE_RESOURCE_GROUP -n $AZURE_APP_NAME --src "./build/app.zip" command creates file containing the value of --src parameter instead of content of that file.

I confirmed that downgrading docker image to 2.76.0 solves this issue.

Related command

az functionapp deployment source config-zip

Errors

No errors

Issue script & Debug output

Command runs successfully, the value of --src parameter is not mentioned in debug output.

DEBUG: urllib3.connectionpool: [https://xxx.blob.core.windows.net:443](https://xxx.blob.core.windows.net/) "GET /function-releases?restype=container HTTP/1.1" 200 0

DEBUG: urllib3.connectionpool: [https://xxx.blob.core.windows.net:443](https://xxx.blob.core.windows.net/) "PUT /function-releases/20250902112340-725d671b-4e31-4d90-8153-b84bf3e26f6f.zip HTTP/1.1" 201 0

Expected behavior

Zip file is uploaded to storage account.

Environment Summary

azure-cli 2.77.0
core 2.77.0
telemetry 1.1.0
Dependencies:
msal 1.34.0b1
azure-mgmt-resource 23.3.0

Additional context

No response

[yonzhan]

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

[dimitor115]

I have the same problem with my Azure Function App CLI deployment, the issue is pretty serious as the deployment itself was successful while the produced ZIP has invalid value as mentioned, which broke our production env for a few hours until we figured out what's happening.

[manasmagdum]

What is the solution for this?
I am using Azure CLI in the azure devops classic releases.

And it is not possible to downgrade the azure-cli version.

Need an urgent fix for this.

Is there any alternative or temporary solution for this?

Thanks in advance.

[manasmagdum]

I have the same problem with my Azure Function App CLI deployment, the issue is pretty serious as the deployment itself was successful while the produced ZIP has invalid value as mentioned, which broke our production env for a few hours until we figured out what's happening.

How did you fix this issue? Any solution other than downgrading version?

I cannot downgrade version as it is on Azure devops agent.

[hevcy]

@manasmagdum I've temporarily worked around this in ADO classic releases by putting a task in the stage that just runs this: pip install azure-cli==2.76.0 and it works for me.