Add child tasks info to orquesta workflow execution json
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
With mistral workflows resulting execution json included all subtasks info including their statuses. It was very convenient for instance for building extended statuses for chatops output with aliases. With orquesta workflows no child info is present in resulting task json except for "children": [ ] array that contains ids only. It would be great to have extended output for subtasks for orquesta workflows similar like it was for mistral ones.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named in the issue. Start by tracing how Orquesta workflow execution results serialize child task IDs and compare that path with Mistral execution output; done when child task details, including statuses, are present in the Orquesta execution JSON.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100