Project

General

Profile

Actions

User story #2145

closed

Allow to not automatically regenerate promises after a modification

Added by François ARMAND over 12 years ago. Updated about 12 years ago.

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

Description

For now, each time a modification related to configurations is made (group modification, PI update, new configuration rule, PT lib reloading, etc), that modification trigger a "deployment", i.e a full regeneration of all the CFEngine promises for each nodes.

We want to make that behaviour configurable so that all "automatic" deployment are delayed until a "manually required" deployment.
That manual deployment will be trigger by the "deploy" button in the top-right "generation" widget.

That widget will have to be updated to display more information:

  • last generation date,
  • number of modification since that generation,
  • list of modifications made since that last generation.

The list of modification could be the list of relevant action log for the considered period.


Related issues 3 (0 open3 closed)

Blocked by Rudder - User story #2151: Separate the deployment trigger in automatic and manual trigger, and based on a parameter, skip automatic deploymentReleasedNicolas CHARLES2011-12-30Actions
Blocked by Rudder - User story #2158: Modify the "Regenerate now" widget to show the number of modification since last modificationReleasedNicolas CHARLES2012-01-03Actions
Blocked by Rudder - User story #2159: Create a popup with the list of modification since last deploymentReleasedNicolas CHARLES2012-01-03Actions
Actions #1

Updated by François ARMAND over 12 years ago

  • Status changed from New to 2
  • Assignee set to Nicolas CHARLES
Actions #2

Updated by Nicolas CHARLES about 12 years ago

  • Status changed from 2 to Pending technical review
  • % Done changed from 0 to 100

It's been achieved through all the others refering tickets

Actions #3

Updated by François ARMAND about 12 years ago

  • Status changed from Pending technical review to 10

Technical review ok.

Actions #4

Updated by Jonathan CLARKE about 12 years ago

  • Category changed from Web - Maintenance to Web - Config management
Actions #5

Updated by Jonathan CLARKE about 12 years ago

Functional review is OK, but I can't close this issue for some reason!

Actions #6

Updated by Jonathan CLARKE about 12 years ago

  • Status changed from 10 to Released

Got it. The "blocked by" issues weren't closed, so I couldn't close this one. Clever Redmine...

Actions

Also available in: Atom PDF