Multiple .env files - only the first one is loaded

[hgeritzer]

Hi,
when there are multiple .env files specified in the dotenv section, only the first existing one is loaded.
Is this expected behaviour?

internal/core/dag.go

// loadDotEnv loads dotenv file
func (d *DAG) LoadDotEnv(ctx context.Context) {

...

	// Load the first found one
	return
}

}

It would be a nice feature to load multiple .env files.

[yottahmd]

Hi,
This is the expected behavior at the moment. Could you describe the cases where you need to load multiple environment files?

[hgeritzer]

hi,
my purpose was to store server credentials in different .env files which could be reused in multiple dags.
for example .env.ssh_server1 , .env.smb_server2, ...

maybe this could be also implemented as additonal secrets provider for properties files? as far as i understood, the secrets provider for files just supports a single key per file?

[ghansham]

One possible solution could be to use sub dag functionality and load dotenv files in those sub dags. I think you can pass these dotenv files as named params in subdags and use those params within subdag to load dotenv files. Request @yottahmd to confirm if dotenv file entry can be a variable within dag (/subdag) context.

[yottahmd]

Yes, making it Sub-DAG works! I also believe we can make the dotenv field more flexible.

dotenv:
  - common.env
  - ["~/.env.dev", "~/.env.prod"]

In this case, both entries are loaded, but only the first matching file among env.dev or env.prod will be applied.