https://dagster.io/ logo
Powered by
a

Auster Cid

09/03/2020, 7:18 PM
Hi guys, I've just reconfigured my instance to use postgre for storage, using env var references to supply the credentials in dagster.yaml. Everything went very smoothly, but now my schedules are failing silently. I'm 99% sure the issue that these new variables dont exist for the cron user, but I'm unsure on how to configure this properly and could use some guidance.
I'm running 
0.9.2
a

alex

09/03/2020, 7:20 PM
there is an 
environment_vars
arg on 
ScheduleDefinition
to get the env vars in to the cron user env
a

Auster Cid

09/03/2020, 7:21 PM
I see, thanks!
a

alex

09/03/2020, 7:21 PM
are failing silently
ya this is not great- there should be a link to the log file that the bash script in the cron tab is set to dump in to somewhere in the scheduler UI, buried somewhere
but since we cant load the instance we can’t write any error events out
a

Auster Cid

09/03/2020, 7:34 PM
maybe this all could be handled by some sort of credential manager? or for a more quick fix, copying all vars in dagster.yaml to schedules by default?
🤷 1
blob thinking 1
ran into a bug in the generated .sh files
Copy code
/opt/dagster/app$ /opt/dagster/dagster_home/schedules/scripts/511db1d235c5857dfaab1d6480dd0b919ee356f3.sh
/opt/dagster/dagster_home/schedules/scripts/511db1d235c5857dfaab1d6480dd0b919ee356f3.sh: line 7: syntax error near unexpected token `('
/opt/dagster/dagster_home/schedules/scripts/511db1d235c5857dfaab1d6480dd0b919ee356f3.sh: line 7: `export DAGSTER_PG_PW=*****(*****'
a

alex

09/03/2020, 9:20 PM
workaround by doing 
{"DAGSTER_PG_PW": '"blahlbah(blah"'}
?
a

Auster Cid

09/03/2020, 9:33 PM
I just changed my password 🤷
🤷 1
a

alex

09/03/2020, 9:33 PM
that works too
4 Views
Powered by