Does workflow scheme support custom field?such as label,output
Open
Nobody has claimed this yet.
stale
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
---
name: aq_detect
description: xxx
runner_type: orquesta
entry_point: workflows/aq_detect.yaml
enabled: true
parameters:
target:
type: "string"
required: true
description: xx
add custom label,and results
---
labels: xxx
results:
output:
type: "string"
required: true
description: xx
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 with the workflow metadata example and the referenced workflows/aq_detect.yaml entry point. Determine whether the workflow scheme can declare custom labels and results fields such as output, and document or implement the supported behavior. Done means the requested fields are accepted and their resulting behavior is demonstrated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100