Just encountered a 404 using azure/webapps-deploy@v2 with the following definition:
- name: Deploy to Azure Web App
id: deploy-to-webapp
uses: azure/webapps-deploy@v2
with:
app-name: '<NAME>'
slot-name: 'Production'
publish-profile: ${{ MY_SUPER_DUPER_SECRET}}
package: .
And it died with
##[debug][POST] https://MY_SUPER_SECRET_SITE:443/api/zipdeploy?isAsync=true&deployer=GITHUB_ZIP_DEPLOY&message=<A REALLY LONG QUERYSTRING ARGUMENT CONSTRUCTED FROM ALL THE COMMIT MESSAGES JOINED TOGETHER TO THE TUNE OF A 2917 CHARACTER LONG URL>
##[debug]Could not parse response body.
##[debug]{}
##[debug]ZIP Deploy response: {"statusCode":404,"statusMessage":"Not Found","headers":{"content-length":"103","connection":"close","content-type":"text/html","date":"Thu, 10 Nov 2022 19:56:46 GMT","server":"Microsoft-IIS/10.0","x-powered-by":"ASP.NET"},"body":"The resource you are looking for has been removed, had its name changed, or is temporarily unavailable."}
Error: Failed to deploy web package to App Service.
Error: Deployment Failed with Error: Error: Failed to deploy web package to App Service.
Any chance you guys can do a max length check on the proposed url it's about to invoke, using the commit messages strung together in the messages querystring arg, to save stupid people like me from themselves?
Just encountered a 404 using azure/webapps-deploy@v2 with the following definition:
And it died with
Any chance you guys can do a max length check on the proposed url it's about to invoke, using the commit messages strung together in the
messagesquerystring arg, to save stupid people like me from themselves?