Project

General

Profile

Actions

Bug #10612

closed

Make node properties editable on the GUI

Added by Janos Mattyasovszky about 7 years ago. Updated almost 2 years ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
84
Name check:
Reviewed
Fix check:
Checked
Regression:

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.

Actions #1

Updated by François ARMAND almost 7 years ago

You are of course right. It is already a planned enhancement

Actions #2

Updated by François ARMAND almost 7 years ago

  • Target version set to 4.1.2
  • Priority changed from 0 to 17
Actions #3

Updated by Jonathan CLARKE almost 7 years ago

  • 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.

Actions #4

Updated by Benoît PECCATTE over 6 years ago

  • Category set to Web - UI & UX
Actions #5

Updated by François ARMAND almost 5 years ago

  • 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.

Actions #6

Updated by François ARMAND almost 5 years ago

  • User visibility changed from Operational - other Techniques | Technique editor | Rudder settings to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 70
Actions #7

Updated by Raphael GAUTHIER almost 5 years ago

  • Target version changed from Ideas (not version specific) to 5.0.12
Actions #8

Updated by Raphael GAUTHIER almost 5 years ago

  • Status changed from New to In progress
Actions #9

Updated by Raphael GAUTHIER almost 5 years ago

  • 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
Actions #10

Updated by Raphael GAUTHIER almost 5 years ago

  • Status changed from Pending technical review to Pending release
Actions #11

Updated by Vincent MEMBRÉ almost 5 years ago

  • Name check set to To do
Actions #12

Updated by Vincent MEMBRÉ almost 5 years ago

  • Fix check set to To do
Actions #13

Updated by Alexis Mousset almost 5 years ago

  • Name check changed from To do to Reviewed
Actions #14

Updated by Félix DALLIDET almost 5 years ago

  • Fix check changed from To do to Checked
Actions #15

Updated by Vincent MEMBRÉ almost 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.12 which was released today.

Actions #16

Updated by Alexis Mousset almost 2 years ago

  • Priority changed from 70 to 84
Actions

Also available in: Atom PDF