-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The new option Clean should have defaulted to false or been highlighted as a breaking change #401
Comments
Since I was storing data files locally, this caused enormous data loss for me. Extremely bad customer service here. How in the world could anyone think the appropriate default setting would be to delete everything without warning?! |
Azure changed their default deployment procedures to delete everything on each deployment, causing complete data loss. See: Azure/webapps-deploy#401
We also experienced data loss due to this "feature". Something that could be as destructive as this should definitely be defaulted to OFF or be a required field - whereas this was optional. |
Another reason why I am still sticking with v2. Sorry about your issues. For some reason there has been eerily silent for quite a while about the issues cropping up, especially in regards to v3. |
Same here, data loss - thank God we had copious backups. |
I can't believe that a new option that deletes existing files has been introduced with a default value that destroys data. |
After upgrading to v3 our deployed app started failing due to being unable to get various javascript files.
It appears that the value for clean is defaulted to true, since on every deployment I only had one set of javascript files. After changing the value explicitly to false I got the expected new set of files for every deployment.
This caused problems for us since previously downloaded SPA apps were looking for older versions of the javascript files. This worked fine in V2.
It would be nice to hightlight this as a breaking change on the relase page rather than just a new feature. Since it can causes issues and is a change in behaviour.
The text was updated successfully, but these errors were encountered: