You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, I work on Azure Functions. I would like to propose that when a user selects an app type of Function App, webdeploy should be the default deployment method.
The main reason for this is that zip based deployment does not put a consumption function app into a consistent state. An action is required to "sync triggers", and if this is not done then the app will not scale properly. When deploying through webdeploy, this step happens automatically.
Defaulting to Remove additional files at destination to enabled. This way, if a user deletes the code for a function from their function app which is deployed through this task, the function will actually be deleted, which is probably what they intended.
The text was updated successfully, but these errors were encountered:
I know there is a lot of confusion around this, but the best thing you should be using is the zipdeploy API.
As for Consumption Linux, it doesn't support any of those (zip, zipdeploy, WebDeploy), so we'll need to come up with alternative (mostly a different discussion).
David just explained this to me, and I now agree with him. I think instead of making webdeploy the default, it would make more sense for the "zip" based default to use the "zipdeploy" API he linked.
@kmkumaran@vincentdass is there already a issue tracking switching over to the "zipdeploy" API? If so we can probably close this..
I come here from Azure/azure-functions-host#2697 where I am a bit confused if I should use zipdeploy or webdeploy now? It has already been 2 years ago but currently still experiencing issues that are described in the referenced issue.
Hi there, I work on Azure Functions. I would like to propose that when a user selects an app type of
Function App
, webdeploy should be the default deployment method.The main reason for this is that zip based deployment does not put a consumption function app into a consistent state. An action is required to "sync triggers", and if this is not done then the app will not scale properly. When deploying through webdeploy, this step happens automatically.
See here for an example of a customer running into this issue:
Azure/azure-functions-host#2499 (comment)
Bonus points for:
https://github.com/davidebbo/AzureWebsitesSamples/blob/61c7b330e83750cd4092625d082340d69f3a54ec/PowerShell/HelperFunctions.ps1#L362-L367
Remove additional files at destination
to enabled. This way, if a user deletes the code for a function from their function app which is deployed through this task, the function will actually be deleted, which is probably what they intended.The text was updated successfully, but these errors were encountered: