500f7d6ad6
The plugin shipped five settings and no page for any of them. The core settings catalog is a hardcoded list a plugin cannot extend, so backups_shareroot and the collection interval were reachable only through the API or a flask shell on the server - which is not a configurable setting in any useful sense, and it is how today went: the setting simply was not there to set. The page is contributed the ADR-010 way rather than by editing core - a card from get_settings_cards plus a route in the plugin's own routes.js, both of which disappear when the plugin is disabled. Filed under Machines, next to Machine Types, because that is where the assets these back up live. It also states the two things the settings do not say for themselves: that health is judged on when a backup was last CONFIRMED rather than when it last changed, and that retention prunes database revisions only - files on the share stay, so enabling it on a share-backed kind leaves orphaned snapshot directories. Snapshot paths are now shown as full UNC text in both places: a Snapshot row on the Marker Contents card, and the existing path on the history page, which gains a copy button. Deliberately NOT a link - browsers refuse to navigate from an https page to file://, so a clickable path looks actionable and silently does nothing, which is worse than no link. Copy, then paste into Explorer. The path comes off the revision, never composed from the configured share root: a snapshot written before the layout changed still lives where it was put.
38 lines
1.6 KiB
JavaScript
38 lines
1.6 KiB
JavaScript
/**
|
|
* Backups plugin routes.
|
|
*
|
|
* One route: the per-asset revision history. The asset-detail panel (ADR-010
|
|
* Path A) lists recent revisions but the generic renderer has no per-item
|
|
* actions, and downloading a .reg needs a per-revision control plus a dialect
|
|
* choice. So the panel links here via its manage link rather than the renderer
|
|
* growing a backups-shaped feature.
|
|
*
|
|
* meta.plugin = 'backups' so the ADR-009 guard redirects when the backend
|
|
* plugin is disabled. requiresAuth because every backups API route is behind
|
|
* JWT + a backups.* permission; an anonymous visit would only render errors.
|
|
*/
|
|
export default [
|
|
{
|
|
// The plugin's five settings had no page at all until this one: the core
|
|
// settings catalog is a hardcoded list that a plugin cannot extend, so
|
|
// backups_shareroot and friends were reachable only through the API or a
|
|
// shell on the server. Paired with get_settings_cards in plugin.py, which
|
|
// puts the card in the rail - both vanish when the plugin is disabled.
|
|
path: 'settings/backups',
|
|
name: 'backups-settings',
|
|
component: () => import('./views/BackupsSettings.vue'),
|
|
meta: { requiresAuth: true, requiresAdmin: true, plugin: 'backups' }
|
|
},
|
|
{
|
|
path: 'backups/asset/:assetid',
|
|
name: 'backups-asset-history',
|
|
component: () => import('./views/BackupHistory.vue'),
|
|
meta: { requiresAuth: true, plugin: 'backups' }
|
|
}
|
|
]
|
|
|
|
// No full-screen routes: every view in this plugin renders inside
|
|
// AppLayout. Declared so routes.gen.js can read `.toplevel` off the module
|
|
// without Rollup warning about a missing export.
|
|
export const toplevel = []
|