Actions
User story #6012
closed
Don't generate promises when we are trivially sur that the modification don't change the generated promises
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
When we create/delete/change Directive/Rule/Groupes, a check is made to see if promises should be regenerated or not
This check can take some time, and there are obvious cases when we can skip the check:- create a group
- create a directive (not attached to a rule)
- change name/description of Directive/Rule/Group
Updated by François ARMAND about 10 years ago
- Status changed from 15 to Pending release
Updated by Vincent MEMBRÉ about 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta2, which were these days.
- Announcement 3.0
- Changelog 3.0
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Updated by François ARMAND over 9 years ago
- Subject changed from Don't generate promises when there are no change that change the generated promises to Don't generate promises when we are trivially sur that the modification don't change the generated promises
Updated by François ARMAND over 9 years ago
- Related to User story #6471: Do not start a policy generation if changes don't require it (dependency graph analysis) added
Actions