WebApp:`az webapp deploy --src-url` should use ARM Proxy

The command az webapp deploy has an optional parameter, --src-url, where the user can specify a remote URL for the file they want to deploy to their Web App. If this parameter is used, the CLI should use the ARM proxy API for the deployment request so that if the user has any networking restrictions such as Private Endpoints or ILB ASEs, then this deployment request will go through the management plane and circumvent any networking restrictions. Today the CLI sends the request directly to Kudu, and does not use this ARM proxy.

• Swagger PR with the API spec: https://github.com/Azure/azure-rest-api-specs/pull/17408/files
• Python SDK release request: https://github.com/Azure/sdk-release-request/issues/2397
  • https://pypi.org/project/azure-mgmt-web/6.1.0/

[jlieow]

Hi,

In case anyone is still struggling with this, I managed to deploy a simple nodejs app to an app service using private endpoints via the workaround az rest command. You may reference this deployment yaml file: https://github.com/jlieow/node-hello/blob/master/.github/workflows/deploy_via_storage_account.yml

The example follows the guide here: https://azure.github.io/AppService/2021/03/01/deploying-to-network-secured-sites-2.html The az rest command was fixed thanks to this stackoverflow thread here: https://stackoverflow.com/questions/71558607/deploy-to-an-azure-web-app-with-a-private-endpoint

[jlieow]

Hi @mpalmahsf. I have not tried it myself but I don’t see why it wouldn’t work. You could try depositing your artifacts into a location which generates a url download link like Google Drive and run the az run command with that url to see if it works.

I tried googling but I don’t think GitHub provides a url to download artifacts during the build process natively which I think is the reason why the guide uses storage accounts.