Skip to content

Fix/deployment catalog widget#15

Merged
BenConstable9 merged 2 commits into
mainfrom
fix/deployment-catalog-widget
Jul 13, 2026
Merged

Fix/deployment catalog widget#15
BenConstable9 merged 2 commits into
mainfrom
fix/deployment-catalog-widget

Conversation

@BenConstable9

Copy link
Copy Markdown
Contributor

Move some hardcoded catalogs / schemas to the widgets

The evaluation and deployment job notebooks derived the catalog (and, in deployment, the personal schema) by parsing model_name, which is fragile and diverges from every other notebook. Use the standard catalog_name and user_schema widgets (with the same interactive fallback the other job notebooks use) and pass both from var.catalog_name / var.user_schema in the deployment job tasks. Regenerate src.
… vars

The ML-outputs schema was called user_schema / user_workspace, but that name is only accurate in development mode. On the clean dev/staging/prod targets there is no per-user prefixing and it resolves to the shared fraud schema, so the name was misleading. Rename the variable to ml_schema and the schema resource key to ml_workspace, matching the layer-role naming of gold_schema and describing what the schema holds (features, model, predictions, monitoring) rather than who owns it.

Also promote bronze_schema / silver_schema / landing_schema to bundle variables (defaults fraud_bronze / fraud_silver / fraud_landing) so every medallion schema is passed through consistently, the same way gold_schema already is, instead of being hardcoded literals in the ingestion workflow. Regenerate src.

Note: renaming the ml_workspace resource key changes its bundle state address, so the first bundle deploy after this recreates that schema.
@BenConstable9
BenConstable9 merged commit cf2b023 into main Jul 13, 2026
2 checks passed
@BenConstable9
BenConstable9 deleted the fix/deployment-catalog-widget branch July 13, 2026 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant