Define when an action plan is stale/invalid
Today in Watcher we generate an action plan after an audit but we never define an expiry date or an event that can invalidate this action plan.
For example we could set a configurable expiration time like 24h that will make all action plan older than 24h no longer valid.
We could also have an invalidation trigger of all action plans when a specific event occurs in the cluster data model. The end of execution of an action plan should also superseed all previous action plans as the cluster state has been modified.
We should add a new state "superseded" for the action plan.
Blueprint information
- Status:
- Complete
- Approver:
- Antoine Cabot
- Priority:
- Medium
- Drafter:
- Antoine Cabot
- Direction:
- Approved
- Assignee:
- licanwei
- Definition:
- Approved
- Series goal:
- Accepted for pike
- Implementation:
-
Implemented
- Milestone target:
-
pike-1
- Started by
- Antoine Cabot
- Completed by
- Alexander Chadin
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Define when an action plan is stale/invalid
Addressed by: https:/
check the state of action plan
Addressed by: https:/
Define when an action plan is stale/invalid
Addressed by: https:/
stale the action plan
