dotenv file path not using var from command line #658

Activity

1. tylermmorton

   added

   bug

   on Jan 22, 2022
2. ghostsquad

   added

   sig/v4

   on May 16, 2022
3. pd93

   removed

   v4

   on Oct 15, 2022
4. matthijsdewit111 commented on Jul 2, 2024

   

   matthijsdewit111

   on Jul 2, 2024

   Last edited by matthijsdewit111

   More actions

   Hope this will be fixed soon, but right now I found 2 possible workarounds.

   The first one is that you can define the dotenv: part on task level, and this works as expected. The drawback is however that you need to duplicate it throughout the taskfile in each task that needs then environment variables. For example:

   version: '3'
   
   vars:
     ACCOUNT: test
   
   tasks:
     print:
       dotenv: [ ".env.{{.ACCOUNT}}" ]
       cmds:
         - echo $TEST_VAR
   

   The other method is the use the strange fact that using variables seems to work ok with in the env: and sh: part. You can read and parse the .env file manually here. Which is very ugly/verbose, but that you only need to do it once in the taskfile. For example:

   version: '3'
   
   vars:
     ACCOUNT: test
   
   env:
     TEST_VAR:
       sh: cat .env.{{.ACCOUNT}} | grep -i "TEST_VAR=" | sed -e "s/TEST_VAR=//"
   
   tasks:
     print:
       cmds:
         - echo $TEST_VAR
   

   (This will also print a warning: cat: .env.: No such file or directory, but it still works. Pretty sure the command gets evaluated twice, once on general setup, and once again for the setup of the task.)
5. pd93

   removed

   type: bug

   on Dec 16, 2024
6. trulede commented on Dec 7, 2025

   

   trulede

   on Dec 7, 2025

   Contributor

   More actions

   Fixed by #2288
7. trulede

   closed this as a duplicateof Taskfile doesn't expand env vars in global variable section #1580 on Dec 7, 2025