and group better, avoid alternating by destroying and restoring
button (prune, file restore, remove) and place file restore and
restore together
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Add 'isPBS' parameter for Restore window so we can detect when to show
the 'live-restore' checkbox.
Includes a warning about this feature being experimental for now.
Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
findRecord does not match exactly, but only at the beginning and
case insensitive, by default. Change all calls to be case sensitive
and an exactmatch (we never want the default behaviour afaics).
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this was partial copied over from PBS, but there we pull out the task
startime alreay when building the store.
As eslint mentions, task was unused, verify_time not defined, fix
that.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
verification column only shows in the backup grid and for
pbs storages
(renderer is mostly copied from proxmox-backup)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
if the checkbox is not checked, we set the value of the vmid filter to ''
but left 'exactMatch' enabled, which means we filter all out where
the vmid is not ''
what we instead want is to remove also the exactMatch so that we
get *all* entries back not *none*
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
instead of hardcoding the text 'type-id-' into the searchbar
to accomodate for the additional size, add an overflowHandler
to the toolbar (for very small display sizes)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Similar to commit 12d50fcd21 which
added this column to the storage content grid let's also add it here.
As we also base off the 'pve-storage-content' it's just a matter of
copying over the column definition 1:1
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Split PVE specific models, which where not moved to the general
widget toolkit, in a separate folder: data/models/
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
some function are now in Proxmox.Utils instead, so we have to use that
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Reviewed-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
most 'Remove' buttons we have used the same code pattern over and over,
with the StdRemoveButton we have a component which does all of this for
us
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Reviewed-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
(NB: the error was only displayed intermittently in the browser console)
The reload call could try a store reload before the store has
a defined url.
The call here is useless since the initial display of
the storage selector compoment will call setStorage() to pass an url
to the store and load it.
Also remove the test on me.store.proxy.url since it was not working
(ExtJS autodefined an URL based on the model name)
this patch moves the onlineHelp ids into the javascript classes, instead
of defining them where we use the classes
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this adds a button to show the configuration of backups
this helps if someone wants to know the details of the
vm in the backup (e.g. name, storages, etc.)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
currently, as soon as you type something in the backup search bar,
the filter for the vm type (e.g. lxc or qemu) gets cleared, and
you see *all* backups (also those not for the current type)
this patch adds the original filterFn to the filter when searching
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
Using ExtJS6 a browser refresh (F5) do not send the 'show' event which we use to display the store as it did with ExtJS4.
At the momment only for tabs inside the datacenter tabpanel, since node and lxc tabpanels are not yet in manager6/