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 #1

Updated by François ARMAND over 8 years ago

  • Related to Bug #8840: Node properties are not being synchronized on the node itself until promises are created/modified added
Actions #2

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions #3

Updated by François ARMAND about 8 years ago

  • Target version changed from 3.1.14 to 4.0.0~rc2
Actions #4

Updated by François ARMAND about 8 years ago

  • Target version changed from 4.0.0~rc2 to 3.1.14

It is a big change on existing workflows, so if we put it in 3.1, we need to hide the behaviour behind a feature switch for existing installation (new installation should have the correct behaviour).

Actions #5

Updated by Jonathan CLARKE about 8 years ago

The feature switch name can be something like "'Backwards compatibility: allow changes to node properties without requiring a Change Request (only applicable if Change Requests are enabled)"

Actions #6

Updated by Jonathan CLARKE about 8 years ago

  • Assignee set to François ARMAND
Actions #7

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions #8

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions #9

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions #10

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions #11

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions #12

Updated by Benoît PECCATTE over 7 years ago

  • Tracker changed from Bug to User story
Actions #13

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions #14

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.20 to 3.1.21
Actions #15

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.21 to 3.1.22
Actions #16

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.22 to 3.1.23
Actions #17

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.23 to 3.1.24
Actions #18

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.24 to 3.1.25
Actions #19

Updated by Benoît PECCATTE about 7 years ago

  • Target version changed from 3.1.25 to 4.1.9
Actions #20

Updated by Vincent MEMBRÉ almost 7 years ago

  • Target version changed from 4.1.9 to 4.1.10
Actions #21

Updated by François ARMAND almost 7 years ago

  • Description updated (diff)
Actions #22

Updated by François ARMAND almost 7 years ago

  • Assignee deleted (François ARMAND)
  • Target version changed from 4.1.10 to Ideas (not version specific)
Actions

Also available in: Atom PDF