You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After receiving responses from Stakwork workflows, the system needs to execute different actions based on the workflow type and response. We need a flexible, maintainable system to map workflow responses to their corresponding handler functions.
Action Registry - defines all actions strings that map to default to "log and exit"
Action Context - typed objects for
Action Handlers - e.g. update user stories, output ticket plan, log and exit
e.g. context
type ActionContext struct {
RequestUUID string // A unique ID for this request
WorkflowID string // Which workflow it came from
Source string // Where it came from
ActionString string // What needs to be done
ResponseData []byte // The actual data to process
}
Assignment Criteria
Strong understanding of Go interfaces and dependency injection
Experience with concurrent operations in Go
Connected on Sphinx V2
Acceptance Criteria
Implement ActionHandler interface
Create ActionRegistry with thread-safe operations
Implement example handlers for:
User story generation
Ticket planning
(Other workflow types as needed)
Add comprehensive unit tests for registry and handlers
Context
After receiving responses from Stakwork workflows, the system needs to execute different actions based on the workflow type and response. We need a flexible, maintainable system to map workflow responses to their corresponding handler functions.
Design
@tobi-bams can you map out a design for this.
e.g:
Action Registry - defines all actions strings that map to default to "log and exit"
Action Context - typed objects for
Action Handlers - e.g. update user stories, output ticket plan, log and exit
e.g. context
Assignment Criteria
Acceptance Criteria
Usage Example
To add a new workflow action:
The text was updated successfully, but these errors were encountered: