Workflow Service Dry Run can do more than just parsing spec
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 260
- Forks
- 57
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 69
Description
What new feature or improvement would you like to see?
Workflow Service Dry Run to include validation and do as much as possible (short of actually submitting). Currently it only parses spec: https://github.com/NVIDIA/OSMO/blob/main/src/service/core/workflow/workflow_service.py#L368-L372
Why is this needed?
Aligns user expectation on "dry-run" > "validate-only".
Allows workflow submission UX improvement in the UI
Code of Conduct
- I agree to follow NVIDIA OSMO's Code of Conduct
- I have searched the open feature requests and have found no duplicates for this feature request
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 in src/service/core/workflow/workflow_service.py at lines 368-372, then trace the current dry-run parsing path and the workflow submission steps it can safely reach. Define which validation and pre-submission work belongs in dry-run without submitting the workflow, and verify that the result supports the intended UI submission experience.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100