Attach custom Task Metadata in Orchesta workflows
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
SUMMARY
I want to be able to attach some metadata to tasks in an orquesta workflow.
something like
start:
action: core.echo message="automation started"
metadata: # some object/string here
next:
- when: <% succeeded() %>
do: task2
Today, action definitions have the ability to define some metadata but it'd be nice to be able to do this at the task level, and access the metadata via the executions api endpoint. Does this sound reasonable for PR/ any alternatives you can think of?
ISSUE TYPE
- Feature Idea
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
Start by reviewing the Orquesta task syntax in the example and the existing action metadata documentation linked in the issue, then trace how task executions are represented by the executions API endpoint. Define the metadata shape and workflow behavior before implementation; done means task-level metadata can be attached and is available through that endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100