Expose signal and waitcondition on the REST API
Registered by
Thomas Herve
To get to a CFN-free world, we need to expose the signal and waitcondition APIs on the native endpoint. Authentication is taken care of separately, for now we can consider that this will work by Icehouse.
Blueprint information
- Status:
- Complete
- Approver:
- Steve Baker
- Priority:
- Medium
- Drafter:
- Thomas Herve
- Direction:
- Approved
- Assignee:
- Thomas Herve
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Steve Baker
- Completed by
- Steve Baker
Related branches
Related bugs
Sprints
Whiteboard
(therve) I have a simple spike here: http://
(stevebaker) I think we would only need a /signal/ path. Native waitconditions could go through that too, we only have 2 in the cfn API for compatibility.
(stevebaker) setting this to i-3 since shardy set native-
(stevebaker) it looks like this was implemented by commit 49f85899cf723af
(?)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
