Ian
01/11/2024, 2:56 PMHenning Holgersen
01/11/2024, 5:22 PMEdgar RamÃrez (Arch.dev)
01/11/2024, 8:26 PMAndy Carter
01/12/2024, 9:10 AMdo you have those same secrets configured in your local environment during development?
Yes, I keep a local .env file that has the secrets in plaintext. That is `git/Dockerignore`'d obvs, and then I make the secrets available as environmental variables in my Container App.Andy Carter
01/12/2024, 9:37 AMIan
01/12/2024, 4:59 PMAndy Carter
01/15/2024, 11:17 AMpip_url
3. Dockerfile - My dbt project is in my full meltano repo. With the stock dockerfile this causes issues as a single line change to a sql file prompts a full docker build to redeploy. I've found some optimisations with layers I will share below.
4. Exposing dagster webserver: On ACA my container command is as belowAndy Carter
01/15/2024, 11:18 AM{
image: '${containerRegistry.name}.<http://azurecr.io/myorg_elt:latest|azurecr.io/myorg_elt:latest>'
name: 'myorg_elt'
env: dagsterEnvSettings
command: ['meltano', 'invoke', 'dagster:dev']
resources:{
cpu: 2
memory: '4Gi'
}
Andy Carter
01/15/2024, 11:18 AMmeltano.yml
I have that as a custom command
- name: dagster
variant: quantile-development
pip_url: dagster-ext dagster-postgres dagster-dbt dbt-postgres dagster-azure pendulum==2.1.2
settings:
- name: dagster_home
env: DAGSTER_HOME
value: $MELTANO_PROJECT_ROOT/orchestrate/dagster
commands:
dev:
args: dev -f $REPOSITORY_DIR/repository.py --dagit-host 0.0.0.0 -d $REPOSITORY_DIR
executable: dagster_invoker
Andy Carter
01/15/2024, 11:20 AMmeltano\orchestrate\dagster\myproj
This means small changes to .sql files don't prompt a full meltano install
which can take a long time.