bug: inconsistent environment variables behaviour #1320
Description
Hello
I tried to use Dagu for the past couple days (awesome work by the way, thank you so much!) and noticed some inconsistencies with environment variables handling between the different ways to execute dags.
First, the environment variables reference does not work for me with manual execution from WebUI or from the scheduler.
The following :
tags: [backup, docker]
schedule: "0 1 * * *"
env:
DIR_DOCKER: ${DIR_DOCKER}
steps:
- name: test 1
command: id
- name: test 2
command: env
- name: cleanup old backups
command: find "${DIR_DOCKER}/data/backup" -type f -mtime +5 -exec rm {} \;fail on 3rd step because ${DIR_DOCKER} is not resolved, which seems to be a bug in this mentioned featured in the doc.
I also tried to run the dags directly from CLI (dagu start myDag.yaml) and it worked but because the all env from my user was passed to Dagu instead of being filtered (as I understand it).
In all three ways of running the dag (manually from the WebUI, with the scheduler and from the CLI), the outputs of the first command were the same (ie. the same user was used to run the commands set).
Thank you in advance for your help on this one :)