[POC] Support Python workflow args in CLI#612
Conversation
Signed-off-by: Oliver Holworthy <1216955+oliverholworthy@users.noreply.github.com>
Linked Issue CheckThis PR does not reference an issue. External contributions must link to Add one of the following to your PR description:
If no issue exists yet, open one See CONTRIBUTING.md |
|
Thank you for your submission! We ask that you sign our Developer Certificate of Origin before we can accept your contribution. You can sign the DCO by adding a comment below using this text: I have read the DCO document and I hereby sign the DCO. You can retrigger this bot by commenting recheck in this Pull Request. Posted by the DCO Assistant Lite bot. |
Stale PR reminderThis PR has had failing checks for 7 days without activity. Failing checks: semantic-pull-request / semantic-pull-request, check, semantic-pull-request / semantic-pull-request, DCOAssistant Please push an update or leave a comment if you're still working on this. To prevent auto-close, add the |
Summary
POC for #507 that makes local Python config workflows executable with custom CLI arguments while keeping the existing
preview,create, andvalidatecommands as the execution surface.This lets a workflow file expose:
and run with:
Design
DataDesignerScriptParamsas the small runtime object passed to Python config modules.load_config_builder()contract for current workflow files.--only to local Python config modules.argparse --helpfrom a workflow as a successful CLI exit instead of a config load failure.Why This PR Is Separate
This is the mergeable base layer. It is independently useful for executable workflow files and gives recipe discovery a clean primitive to build on later.