notification listener should have exchange information available
Registered by
Tong Li
currently oslo.messaging invoked endpoint without passing exchange, queue, routing_key. It will be very useful to have these information in the ctxt or metadata so that endpoint can process the messages accordingly.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Tong Li
- 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
(?)