Merge metadata into the queue's endpoint
During Icehouse, we decided to pull the metadata out of the queue
endpoint by adding a new endpoint `/metadata`. This worked well because
we didn't have a clear view of what the scope of metadata is. Now that
we want to use it and make it a key piece of the queues, we've found
that the workflow is not as clear as we'd like. The reason being that
some key items of the metadata - flavor, for example - need to be
specified during the queue creation and not after.
Blueprint information
- Status:
- Complete
- Approver:
- Flavio Percoco
- Priority:
- Medium
- Drafter:
- Flavio Percoco
- Direction:
- Needs approval
- Assignee:
- Flavio Percoco
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Flavio Percoco
- Completed by
- Flavio Percoco
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Merge metadata back into the queue endpoint
Gerrit topic: https:/
Work Items
Dependency tree
![](deptree.png)
* Blueprints in grey have been implemented.