Resource object refatcor
Registered by
wangxiyuan
We meet some problems now about. It includes:
1. metadata overuse.
a. now we set a lot of reserved metadata for the queue. It's not suitable for metadata usage.
b. we have some different queue usage: delay, subscription, dead letter. It's difficult to distinguish.
2. metadata and options are too mixed to use.
we set some key-pairs in metadata and some others in options. It's inconsistent.
We should refactor the resource, especially the queue, to solve the problem mentioned above.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- wangxiyuan
- 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
Gerrit topic: https:/
Addressed by: https:/
Resource object refactor
(?)
