Project

General

Profile

Actions

User story #8848

open

Node properties update should create a change request

Added by François ARMAND over 8 years ago. Updated almost 7 years ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Web - Config management
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Node Properties as extremelly important for node configuration, because they can impact ndoe groups, and as of http://www.rudder-project.org/redmine/issues/6733, they are also used to directive parameters or ncf parameters.

So they should follow the same workflow as other configuration udpates.

We must also define a clear semantic of what happens when properties are set in non-interactive mode (ex: datasources plugins). Most likely, workflow should only check user-based/interactive changes.


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #8840: Node properties are not being synchronized on the node itself until promises are created/modifiedReleasedVincent MEMBRÉ2016-08-12Actions
Actions

Also available in: Atom PDF