Skip to content
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

Update Backup step #1

Merged
merged 1 commit into from
Jul 22, 2016
Merged

Update Backup step #1

merged 1 commit into from
Jul 22, 2016

Conversation

santiph
Copy link
Contributor

@santiph santiph commented Jul 22, 2016

  • New Backup page on Upgrade flow
  • Fix module references on couple of files

@santiph santiph merged commit 3cb4a4c into master Jul 22, 2016
santiph pushed a commit that referenced this pull request Sep 13, 2016
@santiph santiph mentioned this pull request Nov 23, 2016
6 tasks
santiph pushed a commit that referenced this pull request Dec 6, 2016
* upgrade: Restore last step on refresh or reopen

When browser window is closed and reopened or refreshed during upgrade flow,
the user should be presented with the most appropriate view of the flow.
The UI will show the page respective for `current_step` as returned by the
status API and/or state stored in browser.

Same mechanism is used to prevent user from jumping to any page in the flow
by manually entering the page URL into the address bar.

* post review changes #1 (to be squashed)

* post review changes #2 (to be squashed)

* post review changes #3 (to be squashed)

* post review changes #4 (to be squashed)

* post review changes #5 (to be squashed)
santiph pushed a commit that referenced this pull request Dec 7, 2016
* upgrade: Landing page refresh handling

When "prepare" step is in progress UI polls for status to detect
when step is finished. The polling is started when user clicks
"Begin Upgrade" button.

When page is refreshed or opened while the step is already running
the UI needs to automatically switch to "waiting" state.

* post review changes #1 (to be squashed)

* post review changes #2 (to be squashed)

* post review changes #3 (to be squashed)

* post review changes #4 (to be squashed)

* post review changes #5 (to be squashed)

* post review changes #6 (to be squashed)
@skazi0 skazi0 deleted the features/upgrade7/backup branch June 16, 2017 08:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant