Remove extra files on deploy about webapps-deploy HOT 11 CLOSED

@kodyang The existing deployment options that you have mentioned is msdeploy, however, we have started using zipdeploy in actions as well as in our newer tasks.
According to the documentation here: https://docs.microsoft.com/en-us/azure/app-service/deploy-zipdeploy Deletes the files left over from a previous deployment. However the zip deploy will only delete files that were part of a previous deployment and are not in the deployment artifact.

from webapps-deploy.

@eaarora-ms your link is 404.

Agree with @kodyang, using azure/webapps-deploy to deploy, it don't remove existing files, making the web app very difficult to debug because of extraneous files (development environment != production web app).

from webapps-deploy.

I believe the correct link is https://docs.microsoft.com/en-us/azure/app-service/deploy-zip

However the zip deploy will only delete files that were part of a previous deployment and are not in the deployment artifact.

@eaarora-ms This hasn't been my experience. My application has always been deployed via GitHub Actions but old project files still existed inside the webapp after they were deleted from my GitHub repo.

from webapps-deploy.

What is the status of this issue? It's very important to start each deployment with a clean (empty) target directory. Currently this is a blocking issue for using webapps-deploy.

from webapps-deploy.

We use Kudu REST API for deployment. there is already bug on kudu team for this. projectkudu/kudu#2822, projectkudu/kudu#3183

from webapps-deploy.

Amruta, that bug was last responded to by the team in 2018.

from webapps-deploy.

@eaarora-ms your link is 404.

Agree with @kodyang, using azure/webapps-deploy to deploy, it don't remove existing files, making the web app very difficult to debug because of extraneous files (development environment != production web app).

for different enviornments you can use slots https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots

from webapps-deploy.

Amruta, that bug was last responded to by the team in 2018.

We are following up with Kudu team for this issue. But currently we are unable to repro this. Can you share repro steps?

from webapps-deploy.

The repro was stated by @kodyang at the top of this issue, and has not changed: "The deployment only creates new files and overwrites existing ones, but does not delete files not part of the deployment"

from webapps-deploy.

Since this issue is on Kudu API which action uses please raise issue under https://github.com/projectkudu/kudu/issues/. Closing the issue.

from webapps-deploy.

Over six years old issue and still not solved? That is terrible, especially if I'm reading php class files in specific folders and performing actions on them using Reflection. Old files, which are no longer in git causing errors because of their different structure.

from webapps-deploy.