87d4e6e068
* add storage route * template out the routes and new raft storage overview * fetch raft config and add new server model * pngcrush the favicon * add view components and binary-file component * add form-save-buttons component * adjust rawRequest so that it can send a request body and returns the response on errors * hook up restore * rename binary-file to file-to-array-buffer * add ember-service-worker * use forked version of ember-service-worker for now * scope the service worker to a single endpoint * show both download buttons for now * add service worker download with a fallback to JS in-mem download * add remove peer functionality * lint go file * add storage-type to the cluster and node models * update edit for to take a cancel action * separate out a css table styles to be used by http-requests-table and on the raft-overview component * add raft-join adapter, model, component and use on the init page * fix styling and gate the menu item on the cluster using raft storage * style tweaks to the raft-join component * fix linting * add form-save-buttons component to storybook * add cancel functionality for backup uploads, and add a success message for successful uploads * add component tests * add filesize.js * add filesize and modified date to file-to-array-buffer * fix linting * fix server section showing in the cluster nav * don't use babel transforms in service worker lib because we don't want 2 copies of babel polyfill * add file-to-array-buffer to storybook * add comments and use removeObjectURL to raft-storage-overview * update alert-banner markdown * messaging change for upload alert banner * Update ui/app/templates/components/raft-storage-restore.hbs Co-Authored-By: Joshua Ogle <joshua@joshuaogle.com> * more comments * actually render the label if passed and update stories with knobs
35 lines
1.1 KiB
JavaScript
35 lines
1.1 KiB
JavaScript
import { addSuccessHandler } from 'ember-service-worker/service-worker-registration';
|
|
import Namespace from '@ember/application/namespace';
|
|
|
|
function getToken() {
|
|
// fix this later by allowing registration somewhere in the app lifecycle were we can have access to
|
|
// services, etc.
|
|
return Namespace.NAMESPACES_BY_ID['vault'].__container__.lookup('service:auth').currentToken;
|
|
}
|
|
|
|
addSuccessHandler(function(registration) {
|
|
// attach the handler for the message event so we can send over the auth token
|
|
navigator.serviceWorker.addEventListener('message', event => {
|
|
let { action } = event.data;
|
|
let port = event.ports[0];
|
|
|
|
if (action === 'getToken') {
|
|
let token = getToken();
|
|
if (!token) {
|
|
console.error('Unable to retrieve Vault tokent');
|
|
}
|
|
port.postMessage({ token: token });
|
|
} else {
|
|
console.error('Unknown event', event);
|
|
port.postMessage({
|
|
error: 'Unknown request',
|
|
});
|
|
}
|
|
});
|
|
|
|
// attempt to unregister the service worker on unload because we're not doing any sort of caching
|
|
window.addEventListener('unload', function() {
|
|
registration.unregister();
|
|
});
|
|
});
|