User story #3002
closedAllow to rollback to a previous configuration policy from the event log screen
Description
Sometimes, we want to go back to a previous state that was working.
On the event log page, we want to be able when selecting one event, to be able to roll back to this state.
Each time, two option must be available:
- restore state before that modification (in case it is that modification that broke the configuration);
- roll back after that modification (in case we know that the last correct state included that configuration).
Only event log related to configuration modification must display that possibility, details below.
That feature will only be available if the rudder.autoArchiveItems option is set to true (else, we don't know to what state we have to roll back). Description of that property should be updated to warn on that dependency. TODO: what message to add ?
Event that should display the roll back option
- rule, directive, group [creation, deletion, update]
- rollback & archive restoration
- TO BE CONTINUED
That ticket is a meta-ticket, implementation tickets follows as sub-tasks.
Updated by François ARMAND almost 12 years ago
- Subject changed from Rollback to a previous configuration state to Aloow to rollback to a previous configuration state from the event log screen
- Description updated (diff)
- Status changed from New to 2
- Assignee deleted (
Vincent MEMBRÉ) - Priority changed from 3 to 1 (highest)
Updated by François ARMAND almost 12 years ago
- Subject changed from Aloow to rollback to a previous configuration state from the event log screen to Aloow to rollback to a previous configuration policy from the event log screen
Updated by François ARMAND almost 12 years ago
- Subject changed from Aloow to rollback to a previous configuration policy from the event log screen to Allow to rollback to a previous configuration policy from the event log screen
Updated by François ARMAND almost 12 years ago
- Status changed from New to 8
- Target version set to 24
Updated by Vincent MEMBRÉ almost 12 years ago
- Status changed from 8 to 13
Work is in progress, backend works pretty well, but there is some things that need to be done before it is over
First : #3102 needs to be completed, without it the git process we won't be able to keep our git synchronized with the actual configuration (ldap)
Second : needs to have some UI upgrade to be easy to use.
Updated by Vincent MEMBRÉ almost 12 years ago
- Assignee set to Vincent MEMBRÉ
- Target version changed from 24 to 2.5.0~beta1
Updated by Vincent MEMBRÉ almost 12 years ago
Pull request done : https://github.com/Normation/rudder/pull/59
It needs #3102 to be accepted before.
Updated by Vincent MEMBRÉ almost 12 years ago
Other pull requests : https://github.com/Normation/rudder-commons/pull/2 for rudder-commons and https://github.com/Normation/cf-clerk/pull/4 for cf-clerk
Updated by Vincent MEMBRÉ almost 12 years ago
packaging pull request : https://github.com/Normation/rudder-packages/pull/10
Updated by Jonathan CLARKE almost 12 years ago
- Status changed from 13 to Pending release
- % Done changed from 20 to 100
Applied in changeset commit:615b293dc557c4e231903a5111e189c64f1ba331.
Updated by Nicolas CHARLES almost 12 years ago
- % Done changed from 20 to 100
Applied in changeset c818bc2137fc0a8f7e722f3325643645a16b8979.
Updated by Nicolas PERRON almost 12 years ago
This ticket should have been ended by bda185eb9bf8a9ab74d6fecc4168e33a493488d1 but is still blocked by #3102
Updated by François ARMAND almost 12 years ago
- Status changed from Pending release to Released