User story #2158
closed
Modify the "Regenerate now" widget to show the number of modification since last modification
Added by Nicolas CHARLES almost 13 years ago.
Updated almost 13 years ago.
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
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!
- Priority changed from 1 (highest) to 2
- Status changed from 2 to Pending technical review
- % Done changed from 0 to 100
- Status changed from Pending technical review to 10
Technical review OK. Perhaps some part could be factorized (XML for sucess/failure ?), but nothing even worthing to open a ticket.
- Status changed from 10 to Released
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by 
Updated by