Project

General

Profile

Actions

User story #6471

open

Do not start a policy generation if changes don't require it (dependency graph analysis)

Added by François ARMAND about 9 years ago. Updated about 6 years ago.

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

Description

In #6012, we implemented a trivial oracle which say if there is a need to regenerate promises or not.

The only changes taken in account for that first oracle where chances who didn't require any analysis on the dependency graph of object, so that we could say if the change will lead to a modification in isolation from anything else.

On that user story, we want to upgrade the oracle so that it can look for simple dependencies and don't generate promises on these cases:

Modification on a rule where both the starting and final state lead to a not applied rule

- modification add / remove directive or change rule parameters when no groups on target
- modification add / remove group or change rule parameters when no directives on target

Change on group not used as target of an applied rule

i.e: any change to a group which is not used to generate promises is free

Change on group where both the starting and final state leads to 0 nodes

Because, well, that doesn't matter much

Change on directive not used as target of an applied rule

same reason than for group

Change in parameter not used

This one may be tricky to decide and may require a full directive parameter analysis.


Related issues 1 (0 open1 closed)

Related to Rudder - User story #6012: Don't generate promises when we are trivially sur that the modification don't change the generated promisesReleasedNicolas CHARLES2014-12-16Actions
Actions

Also available in: Atom PDF