Project

General

Profile

Actions

User story #6012

closed

Don't generate promises when we are trivially sur that the modification don't change the generated promises

Added by Nicolas CHARLES over 6 years ago. Updated about 6 years ago.

Status:
Released
Priority:
N/A
Category:
Performance and scalability
Target version:
Suggestion strength:
User visibility:
Effort required:

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

Subtasks 1 (0 open1 closed)

User story #6017: Don't automatically trigger a check of promises regeneration when changes don't require itReleasedFrançois ARMAND2014-12-16Actions

Related issues

Related to Rudder - User story #6471: Do not start a policy generation if changes don't require it (dependency graph analysis)NewActions
Actions #1

Updated by François ARMAND over 6 years ago

  • Status changed from New to 15
Actions #2

Updated by François ARMAND over 6 years ago

  • Status changed from 15 to Pending release
Actions #3

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.0.0~beta2, which were these days.

Actions #4

Updated by François ARMAND about 6 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
Actions #5

Updated by François ARMAND about 6 years ago

  • Related to User story #6471: Do not start a policy generation if changes don't require it (dependency graph analysis) added
Actions

Also available in: Atom PDF