Update deployment-zip-push.md

[Aghyad85]

add extra details about preserved files in zip deploymet

[prmerger-automator]

@Aghyad85 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit f07bce8:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/azure-functions/deployment-zip-push.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@ggailey777

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[im-samz]

This was a bit confusing as the two sentences seem contradictory at first glance.
If I understand correctly, the first sentence states that any files not found in the zip will be deleted. The second sentence states that certain files and directories uploaded by FTP or created by the app with be preserved nonetheless. If so, let's focus the second sentence on what causes certain files/directories to be preserved.

i.e.,
"...app. However, any files and directories added to the site via FTP or by your app during runtime will be preserved."

^ Is this technically correct?

[Aghyad85]

Yes, this is correct based on the below link :

https://github.com/projectkudu/kudu/wiki/Deploying-from-a-zip-file-or-url#comparison-with-zip-api

When a new build is deployed with zipdeploy, files and directories that were created by the previous deployment(made via zipDeploy) but are no longer present in the build will be deleted. Any other files and directories found in the site that aren't being overwritten by the deployment, such as those placed there via FTP or created by your app during runtime, will be preserved. e.g. a previous folder 'BackupLogs' created from an FTP upload or manual creation would be preserved even if the zip doesn't contain this folder.

[im-samz]

Can we use this?

When you use .zip deployment, any files and directories from the previous deployment that aren't found in the deployed .zip file are deleted from your function app. Files and directories that do not originate from a .zip deployment, such as those added to the site via FTP or by your app during runtime, will be preserved.

[im-samz]

^ just making clear what files/directories get deleted and what gets preserved.
I don't think we need to the example for brevity sake.

[ggailey777]

Let's try to avoid discussing FTP 😉

Suggested change

	> When you use .zip deployment, any files from an existing deployment that aren't found in the .zip file are deleted from your function app.Any other files and directories found in the site that aren't being overwritten by the deployment, such as those placed there via FTP or created by your app during runtime, will be preserved.
	> When you use .zip deployment, any files from the previous deployment are either deleted or updated during a subsequent deployment to your function app. Other files and directories in your function app that weren't part of the previous deployment are maintained.

[im-samz]

I like this!