gsoc26: Declarative Workflow Engine (chaining download, deploy, delete) - #84
gsoc26: Declarative Workflow Engine (chaining download, deploy, delete)#84DhanashreePetare wants to merge 5 commits into
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Integer-Ctrl
left a comment
There was a problem hiding this comment.
All workflows working (with own credentials)
| @@ -0,0 +1,16 @@ | |||
| # Example Workflows | |||
|
|
|||
| Three example workflow pipelines, each runnable directly. All three use real, existing Databus data as their download source. | |||
There was a problem hiding this comment.
each runnable directly
Not really since it uses your account :D
But okay. Maybe re-phrasing in the clean-up phase after this PR
Pull Request
Description
Adds a declarative workflow engine:
databusclient workflow run pipeline.ymlruns a sequence of download/deploy/delete steps defined in YAML, with output chaining between steps (${steps.name.output_files}/${steps.name.output_urls}) and per-step error handling (fail/continue/retry).Related Issues
Issue #79
Type of change
Checklist:
poetry run pytest- all tests passedpoetry run ruff check- no linting errorsOne open design question raised with mentor separately: deploying a file that was downloaded and converted (
--format/--compression) during a workflow step has no clean path yet, since the converted file only exists locally anddeployneeds a fetchable URL. Deploying the original, unconverted download URL (via the newoutput_urlsstep output) works today and is tested.