Bug #10612
closed
Make node properties editable on the GUI
Added by Janos Mattyasovszky over 7 years ago.
Updated over 2 years ago.
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Description
Now with 4.1 one has the possibility to save/delete node properties (after #10569 even in json format), but there is no easy way to edit an existing one if you happen to have a complex json structure in one property.
Suggestion is to have an edit button, that will copy the current value of the key into the input form, and on submit overwrite the value of the existing property.
You are of course right. It is already a planned enhancement
- Target version set to 4.1.2
- Priority changed from 0 to 17
- Tracker changed from Bug to User story
- Target version changed from 4.1.2 to Ideas (not version specific)
Of course, this must be made available, and it would be a lovely convenience. For now it's an easy workaround to copy/paste the value, delete the old property and re-add it.
As such I can't consider this a bug, it's a feature request, and we won't be including it in 4.1.*. Requalifying and targeting for future development.
- Category set to Web - UI & UX
- Translation missing: en.field_tag_list set to Sponsored
- Tracker changed from User story to Bug
- Assignee set to Raphael GAUTHIER
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- Priority set to 0
This is actually a bug because if you want to change a node property without having a bad version of policies generated between the "delete" and "add it back corrected", you need to:
- change node to audit mode,
- delete property
- add property
- change node mode to enforce back
Without that you may break the production.
- User visibility changed from Operational - other Techniques | Technique editor | Rudder settings to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 70
- Target version changed from Ideas (not version specific) to 5.0.12
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2276
- Status changed from Pending technical review to Pending release
- Name check changed from To do to Reviewed
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.12 which was released today.
- Priority changed from 70 to 84
Also available in: Atom
PDF
Updated by 
Updated by Jonathan CLARKE 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by