[POC] Add Data Designer recipe discovery#613
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. |
Signed-off-by: Oliver Holworthy <1216955+oliverholworthy@users.noreply.github.com>
d9a6c90 to
0cf8039
Compare
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 layered on top of #612 that lets installed packages register Data Designer recipes without DataDesigner core depending on any specific recipe repository.
External packages can register a named recipe with the
data_designer.recipesentry point group. Data Designer can then inspect and execute those recipes through the normal generation verbs:data-designer recipes list --output json data-designer recipes show retrieval-sdg --output json data-designer recipes help retrieval-sdg data-designer preview --recipe retrieval-sdg -- --input-dir ./docs data-designer create --recipe retrieval-sdg -- --input-dir ./docsDesign
data_designer.recipesentry point group as the external registration mechanism.data-designer recipes list,show, andhelpfor human and agent inspection.load_config_builder(params)for execution.build_typer_app()so Data Designer can surface recipe-specific help and structured argument metadata from the same Typer command shape used for execution.argparseparser inspection as a compatibility fallback for simple external recipes, but the POC consumer in DataDesignerPlugins uses Typer.Review Notes
This PR currently includes the #612 commit because the base branch is in a fork. The recipe-discovery work is the top commit. Once #612 lands, this can be rebased so the diff contains only the recipe registry and inspection layer.