Project

General

Profile

Actions
Copy link

User story #6017

closed

User story #6012: Don't generate promises when we are trivially sur that the modification don't change the generated promises

Don't automatically trigger a check of promises regeneration when changes don't require it

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

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Performance and scalability
Target version:
3.0.0~beta2
Pull Request:
https://github.com/Normation/rudder/p...
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

when we change/create/delete an object, we always trigger a check of promises generation

This ticket deals with the "obvious" cases:
- creation of a group
- creation of a directive
- modification of name/description of group/directive/rue/parameter

Since most of the modification goes through the changeRequestService, most checks lives in the CommitAndDeployChangeRequest

Actions
Copy link
 #1

Updated by Nicolas CHARLES over 9 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from Nicolas CHARLES to François ARMAND
  • Pull Request set to https://github.com/Normation/rudder/pull/731
Actions
Copy link
 #2

Updated by Nicolas CHARLES over 9 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ over 9 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
Copy link
 #5

Updated by Benoît PECCATTE about 9 years ago

  • Tracker changed from Enhancement to User story
Actions
Copy link

Also available in: Atom PDF