-
Notifications
You must be signed in to change notification settings - Fork 14
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
Non-disruptive Ziti Desktop Edge Updates #474
Comments
WDE already supports the points 1 and 3. The second point is something that we need to discuss further. |
If we can leave a day or two's time for point 1 - it would be more user friendly. The manual update window is quite short. In other words, on point 2 - give the user time for a week to update |
|
This was referenced Jun 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The auto update / installation process in ziti deskop edge is service disruptive where the ziti service and the ongoing connections are terminated as part of the upgrade process. The user is therefore forced to lose their application connections or data rather than being able to choose when they wish to update. Can we do our software update like how windows does it - 1. Allow user to manually update 2. Update at set time / after - ex after x / y/z/ hours that the user can select 3. Allow it to update as per the notification. As orgs start using us for critical apps / traffic, we should handle updates that can be controlled by users such that it doesn't disrupt their work.
The text was updated successfully, but these errors were encountered: