WBE endpoints constructors
Currently workers when creating tasks have a restriction on the objects they create in that those objects can not take any type of customized constructor parameters (besides name), when constructing a flow and executing it on remote workers this is non-obvious that the constructed flow (which may have had customized constructor parameters) will not work on the wbe engine.
Perhaps we can make this better by sending how the task was constructed (those customized params) when a remote worker is requested to do a task (this of course can't handle any complicated resource like objects).
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- Greg Hill
- Direction:
- Approved
- Assignee:
- Greg Hill
- Definition:
- Approved
- Series goal:
- Accepted for 0.3
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Greg Hill
- Completed by
- Joshua Harlow
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
add the ability to inject arguments into tasks at task creation
