Menu
Deploy generated DAGs to a target directory
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Manage GizmoSQL processes: start, stop, list, and stop-all DuckLake-backed SQL servers
Create or modify database connections in application.sl.yml
Manage Quack DuckDB query servers exposing DuckLake over a thin remote protocol — serve (foreground), start/stop/list/stop-all (background)
Automatically infer schemas and load data from the incoming directory
Data quality expectations syntax, built-in macros, and validation patterns
Apply Row Level Security (RLS) and Column Level Security (CLS) policies
| name | dag-deploy |
| description | Deploy generated DAGs to a target directory |
Deploys previously generated DAG files to a target directory (e.g., your Airflow DAGs folder or Dagster repository). Supports cleaning the target directory and organizing files into subdirectories.
starlake dag-deploy [options]
--inputDir <value>: Folder containing DAGs previously generated by dag-generate--outputDir <value>: Root deployment directory for all DAGs (required)--dagDir <value>: Subdirectory within outputDir for DAG files--clean: Delete the output directory contents before deploying--reportFormat <value>: Report output format: console, json, or htmlstarlake dag-deploy --outputDir /opt/airflow/dags --clean
starlake dag-deploy --outputDir /opt/airflow/dags --dagDir starlake
starlake dag-deploy --inputDir /tmp/generated_dags --outputDir /opt/airflow/dags