Project

General

Profile

Actions

Bug #10301

closed

Remove "rights" in node property

Added by François ARMAND about 7 years ago. Updated over 5 years ago.

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

Description

For now, we don't really know what "rights" mean for node properties. Is it permissions? Is it some kind of ownership? Something else?
This is mostly due to the fact that we don't have real permissions at that granylarity for now in Rudder, and that we have only two cases for node properties: provider defauls => "the user or datasources plugin can change it", "provider datasource => only datasources plugin can change it".

So, for now, we propose the following enhancement: only add the "provider" property, and add that restriction: "when provider is defined and not equals to "defauls", the node property is only updatable by the provider of the defined kind". That captures pretty well the constraint we want to define without frozing any other dimension. It will be easier to latter add a real permession management on top of that.


Subtasks 1 (0 open1 closed)

Bug #10316: Missing import deletion about rights, breaks compilationReleasedVincent MEMBRÉActions
Actions #1

Updated by François ARMAND about 7 years ago

  • Translation missing: en.field_tag_list set to Blocking 4.1
Actions #2

Updated by François ARMAND about 7 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/1538
Actions #3

Updated by François ARMAND about 7 years ago

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

Updated by Vincent MEMBRÉ about 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.0~rc1 which was released today.

Actions

Also available in: Atom PDF