I'm trying to do a zip deploy for function app. Because my Function App is firewalled inside VNet, az cli fails so I'm following Kudu documentation to deploy manually. I have a bash script
CREDS="..from publish profile..."
SCMURL="https://${fnapp}.scm.azurewebsites.net/api/zipdeploy"
echo "deploy zip ${SCMURL}"
curl --fail -X POST -H "Content-Type:application/zip" -u "$CREDS" -T functionapp.zip "$SCMURL" || exit 1
and I get a response
deploy zip https://func-mytestsomething-001.scm.azurewebsites.net/api/zipdeploy
curl: (22) The requested URL returned error: 404
All the examples I've seen use exactly this URL.
If I do the same against /api/publish?type=zip I get an OK response, but the functions never get deployed, even if I do manual syncing and restart.
My SKU is flex consumption, does that make the situation somehow special?
I think my zip package is fine, because it is deploying ok when using az cli or github action. For my use case, I would just need to use kudu api.
az functionapp deployment source config-zipinstead from inside the VNet.config-zipcalls under the hood? clearly that works from outside the vnetzip deploymentcommands: 1.tar -a -c -f functionapp.zip *to zip your project. 2.az login3.az functionapp deployment source config-zip --resource-group <ResourceGroupName> --name <FunctionAppName> --src functionapp.zip