Bug #22502
closed
Group creation must be subjected to change-request
Description
A group creation, without being afected to a rule can still change policy generated thanks to:
- group properties
- even without group properties, by changing priority order of subgroups and thus policy inheritance.
=> we need to always create a CR for new group
Updated by François ARMAND almost 2 years ago
- Related to Bug #22503: Add a property to validate all change added
Updated by François ARMAND almost 2 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND over 1 year ago
I didn't found a way to make it matters with inheritance and properties:
- it can't change parent properties (and since it's newly created, it can't be assigned to a rule);
- it could resolve a conflict between two groups (https://docs.rudder.io/rudder-by-example/current/policies/hierarchical-variable-conflict-resolution.html#_overriding_conflict_and_conflict_resolution) but it can't change and existing resolved conflict just by being created.
I believe that problem does not happen with group creation.
Group import are an other beast, but they are out of scope.
Updated by François ARMAND over 1 year ago
- Status changed from In progress to Rejected
Rejecting, we will open it again in case someone find a valid use case for that.