The promotion workflow
1
Create a workspace and make your changes
Start with a workspace scoped to your work. Run scrapers, update schemas, edit SQL models, and validate extraction results — all within the workspace.
2
Validate your changes
Before promoting, confirm the data looks correct. Use
warehouse_query to inspect results and workspace_manage(operation="list") to review the workspace state.Read-only operations don’t require a workspace_id, but you can pass one to scope queries to your workspace data.3
Promote the workspace
When you’re satisfied, promote:The response confirms promotion has started:
What promotion does
Promotion runs several steps in sequence:- Pushes data to production — for scraper-based workspaces, all rows added or modified since the workspace was created are upserted into the production schema. Rows deleted in the workspace are removed from production.
- Promotes SQL models — the latest version of every SQL model edited in the workspace is written to production.
- Promotes scraper and extractor code — any scraper or extractor code edited in the workspace is promoted alongside the data.
- Materializes gold and platinum tables — views and tables downstream of your changes are rebuilt in the warehouse. This step may take several minutes depending on how many models depend on your changes.
SQL models are synced to GitHub automatically each time you save them with
sql_model_save. Promotion applies those changes to the live production warehouse — it doesn’t re-sync to GitHub.After promotion
Once promoted, the workspace is locked:- It appears with a
[PROMOTED]label inworkspace_manage(operation="list") - It cannot be deleted
- No further changes can be made to it