Project

General

Profile

Actions

User story #17227

closed

Prevent removal of 'system' global and group properties

Added by François ARMAND about 4 years ago. Updated almost 4 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
To do
Fix check:
Checked
Regression:

Description

We want to provide a rudder global (and perhaps for group) property with important default properties. Not having them would broke rudder. So we don't want an user to be able to change/delete them.

We propose to use the same `provider` system than for node properties, with the following new set of rules addapted to inheritance:

- for a given object (global, group, node), only the same provider can change an existing property appart if that provider is the default one in which case any provider can update the property and set themself as providier (ie: same rule as before, but for group and global in addition to node),
- provider don't change semantic of inheritance and overriding: a property with a provider different from default can be overriden by any provider, and at each level, fully inherited properties (ie virtual one, which are not really on that object) get an "inherited" provider.


Related issues 2 (0 open2 closed)

Related to Rudder - User story #16347: Group propertiesReleasedNicolas CHARLESActions
Related to Rudder - Bug #18763: '5fd350e5 UNKNOWN attributeDescription "TARGETNAME" inserted' after migration to 6.2RejectedActions
Actions #1

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.0~beta1 to 6.1.0~beta2
Actions #2

Updated by Vincent MEMBRÉ almost 4 years ago

  • Subject changed from Some defautl global and group properties should not be deletable to Prevent removal of 'system' global and group properties
Actions #3

Updated by Vincent MEMBRÉ almost 4 years ago

  • Parent task deleted (#16347)
Actions #4

Updated by Vincent MEMBRÉ almost 4 years ago

Actions #5

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.0~beta2 to 6.1.0~beta3
Actions #6

Updated by François ARMAND almost 4 years ago

  • Status changed from New to In progress
Actions #8

Updated by François ARMAND almost 4 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/2953
Actions #9

Updated by François ARMAND almost 4 years ago

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

Updated by Vincent MEMBRÉ almost 4 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.1.0~beta3 which was released today.

Actions #11

Updated by François ARMAND almost 4 years ago

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

Updated by François ARMAND over 3 years ago

  • Related to Bug #18763: '5fd350e5 UNKNOWN attributeDescription "TARGETNAME" inserted' after migration to 6.2 added
Actions

Also available in: Atom PDF