User story (meta) #2158

Modify the "Regenerate now" widget to show the number of modification since last modification

Added by Nicolas CHARLES almost 3 years ago. Updated almost 3 years ago.

Status:Released Start date:2012-01-03
Priority:2 Due date:
Assignee:Nicolas CHARLES % Done:

100%

Category:Webapp - Display, home page
Target version:2.4.0~alpha3 Estimated time:5.00 hours
Needs translating:No

Description

When not in automatic deployment, the "regenerate now" should display the number of modification since the last deployment.
The type of modification that are considered modification will probably need to be refined

Caution : there might be a slight problem with the exact date of last deployment, we'll need to use the starttime of deployment, but it's only at endtime that we know if the deployment was a succes


Related issues

blocks Rudder - User story (meta) #2145: Allow to not automatically regenerate promises after a mo... Released 2011-12-23

Associated revisions

Revision 0c7baab3
Added by Nicolas CHARLES almost 3 years ago

Fixes #2158 : when in manual deployment, the widget show the number of modifications since last successful deployment. It has the side effect of always showing the last deployment date, even if it was before the reboot of the app

History

#1 Updated by Jonathan CLARKE almost 3 years ago

Nicolas CHARLES wrote:

When not in automatic deployment, the "regenerate now" should display the number of modification since the last deployment.
The type of modification that are considered modification will probably need to be refined

Let me start this refining off by suggesting a few off the top of my head:
  • Commits to the git repo affecting policy template versions in use by applied CRs (ie, changes in PTs)
  • Changes to values in existing PIs that are included in applied CRs (the parameters in a given PI, if the PI is in use by an applied CR)
  • Changes in the list of members in groups that are targets for applied CRs (ie, nodes added or removed)
  • Newly applied CRs
  • Newly added PIs to already applied CRs
  • Changes to the Rudder server configuration (ie, allowed networks, server IP...)

This list is just a start, it may not be exhaustive!

#2 Updated by Jonathan CLARKE almost 3 years ago

  • Priority changed from 1 to 2

#3 Updated by Nicolas CHARLES almost 3 years ago

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

#4 Updated by François ARMAND almost 3 years ago

  • Status changed from Pending technical review to Pending functional review

Technical review OK. Perhaps some part could be factorized (XML for sucess/failure ?), but nothing even worthing to open a ticket.

#5 Updated by Jonathan CLARKE almost 3 years ago

  • Status changed from Pending functional review to Released

Looking good!

Also available in: Atom PDF