The backend treats an undefined value and 0 differently. If the option
is undefined, it will still be set for Windows in config_to_command.
Replace the checkbox with a combobox covering all options.
Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
In clusters a storage was pushed as many times as there are nodes
using it. Ensure we only push a path once, do this with a memory
oriented solution, i.e., build a extra object to remember what we
already pushed. This is preferred over a me.findExact call as it's a
o(n) vs o(n^2) solution compute wise and we make the user wait if
this would need long, so reducing compute time over memory use is
here a good choice - even if we will seldom run into situations where
this actually will make a difference with such small data counts.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
I saw some cases where the pending changes just continued to get
triggered for some VMs, even if they shouldn't anymore - effectively
resulting in 3 - 4 concurrent pending changes call at a time.
It could be this, or not, but it's cleaner this way so go for it
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
Avoids that the user selector always pops up and tokenid is normally
more likely to change as the userid gets pre-selected to the one from
the logged in user.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
As else some people could be confused and put in their name, as below
is the email field, and name+email are quite often pairs.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
by increasing the space for the link, and using a boxLabel instead
of fieldLabel, which has better spacing for longer text
also move the e-mail before the directory to have all textboxes together
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
When using a diffstore, we have to specify all fields that are
displayed, otherwise the store does not know which fields to check for
change
for the acme plugin view, 'api' was missing
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
we cannot pass 'delete' on create api call, and we have to make
sure that 'default_opts' and 'sync_attributes' are alwyas available,
since they are used in onGetValues
(they were only created during setValues, which is not called
when adding a new realm)
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
this is not a synchronous api call, so open a taskprogress window
and reload after the task is done
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
if we use a diff/update store combo, we have to load the updatestore
not the diff store, else we get spurious empty grids
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
if the 'default' account exists, make the name field required and
remove the emptytext
get the information by querying the grid store. this may be not
up-to-date, but it is less intrusive that an extra api call that
blocks the window
Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>