Rudder

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.