Emit start and end versioned notifications at the start and at the end of the given action
The bug https:/
The aim of this bp is:
* to define the rules where the start and end notifications should be placed in the code path. E.g. most of the instance action start notifications are emitted from the compute/manager not from the REST API where the action is initiated. But in the other hand instance.delete in case of local delete is emitted from compute/api
* think about using decorator and / or a context manager to send notifications at function enter/exit/error
* to go through the versioned notifications and make them consistently placed
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Balazs Gibizer
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
This is a backlog blueprint not intended to be implemented in Rocky -- gibi 2018.04.18