- do you all remember what it was like having to worry about a trailing comma at the end of a select clause? asking for a friend
COMING SOON 🚧
TODO: want to make the DAGSTER_HOME dynamic
in ./cese_dia_dagster/cese_dia_dagster is an .env file change DAGSTER_HOME to your location (has to be absoloute path for local dev)
note if a dagster.yml file exists in DAGSTER_HOME location then dagster will use that for instance config.
For more information on dbt:
- Read the introduction to dbt.
- Read the dbt viewpoint.
- Join the dbt community.
Generate documentation for the project:
$ dbt docs generate
View the documentation for the project:
$ dbt docs serve
dbt codegen allows us to automatically generate source, and staging tables and staging yaml without having to write all the columns manually 🚀
simply run the dagit ui in debug mode in vscode via .vscode/launch.json:
{
"version": "0.2.0",
"configurations": [
{
"name": "Dagster: Debug Dagit UI",
"type": "python",
"request": "launch",
"module": "dagster",
"justMyCode": false,
"args": ["dev",
"-f",
"${workspaceFolder}/cese_dia_dagster/cese_dia_dagster/definitions_example_delta_azure.py"
],
"envFile": "${workspaceFolder}/.env"
}
]
}
This way we skip spinning up the dagster UI saving time when developing. But we still want to test with the dagit UI before deployment.
You just need to change which assets you want run in ./debug
debug mode in vscode via .vscode/launch.json:
{
"version": "0.2.0",
"configurations": [
{
"name": "Dagster: debug with .debug.py",
"type": "python",
"request": "launch",
"cwd": "${workspaceFolder}/cese_dia_dagster",
"module": "debug",
"justMyCode": false,
"envFile": "${workspaceFolder}/.env",
},
}
pip install dagster==1.6.0 dagster-webserver==1.6.0 dagster-dbt==0.22.0 dagster-duckdb==0.22.0 dagster-duckdb-pyspark==0.22.0 dagster-duckdb-pandas==0.22.0 dagster-deltalake-pandas==0.22.0 dagster-aws==0.22.0