Option to propagate DPU template settings to all/selected instances

[jakubklimek]

All DPU instances should have an option to choose

1. whether they should have the same settings as the template they come from - when template settings changes, so does theirs
2. whether they should have their own settings - when DPU template settings changes, their does not.

This should be realized by a checkbox that switches this behavior.

Minimalistic version is a button that propagates template settings to all instances. It can use the DPU template ID in the following simple SQL query:

UPDATE unifiedviews.dpu_instance AS t JOIN unifiedviews.dpu_template AS s on s.id = <DPU TEMPLATE ID>
 SET t.configuration = s.configuration
 WHERE t.dpu_id = s.id;

[skrchnavy]

Proposed solution (as discussed via skype)

• checkbox in DPU instance to switch between configuration from template and from instance
• when checked, instance configuration is displayed but is not editable.
• Instance configuration is not updated when tempolate configuration is used
• 'Copy from template' button allows user to replace instance configuration with template configuration.

[skodapetr]

Just a note: rather then "not editable" I would use term "can not be saved".
As configuration dialog is created and managed by DPU, disabling every component may be possible but seems to me like unnecessary effort.

A label that announce fact that this is "read only" dialog, may also be considered.

[skodapetr]

I merged this feature into developUK and it looks like it's OK - besides some dialog miss layouts. We will test it as soon as we deploy developUK.

[ghost]

import export!

On 10/31/2014 03:20 PM, Petr Škoda wrote:

I merged this feature into developUK and it looks like it's OK -
besides some dialog miss layouts. We will test it as soon as we deploy
developUK.

—
Reply to this email directly or view it on GitHub
#132 (comment).

[skrchnavy]

fixed in beec69c