Env merging

[joeblew999]

Description

I declared a few .env files in my project , and I was hoping that it would merge their variables at runtime .

It’s does not seem to though .

In this case the .env files are in the same folder as the task file .

It would be even cooler if it would do the merging upwards towards the root of the repo .

[joeblew999]

I take it back :)

dotenv: ['dev.env', 'operator.env', '{{.ENV}}/.env', '{{.HOME}}/.env']

It does see the env values in both dev.env and operator.env when they are in the same folder as Taskfile. If the NAME / Value pairs are the same in both .env files, it has to pick one, which is non deterministic - No Idea how we should handle this.

If I move operator.env up one folder level if does NOT see it though. So it's not able to look up the folder tree to the git root.

Not sure if this if looking up the folder tree is likely to be wanted or not ? For the type of projects we do its useful

[pd93]

If the NAME / Value pairs are the same in both .env files, it has to pick one, which is non deterministic

This should be deterministic. It should read the files in order and apply values on top of any existing values. You should end up with the same result every time you run a task.

If I move operator.env up one folder level if does NOT see it though. So it's not able to look up the folder tree to the git root.

Dotenv directives require a path to a specific file. They do not search up the file tree.

[joeblew999]

thanks you for the clarification.

I know it's hard to describe everything in the docs.

If you want help on the docs, let me know, as I have a large team using task and its worth it to me.

[joeblew999]

If the NAME / Value pairs are the same in both .env files, it has to pick one, which is non deterministic

This should be deterministic. It should read the files in order and apply values on top of any existing values. You should end up with the same result every time you run a task.

But what order ? Alphabetical or maybe the order Task loaded them ?

Yes it's acting deterministically thankfully. Dont want acts of spooky :)

If I move operator.env up one folder level if does NOT see it though. So it's not able to look up the folder tree to the git root.

Dotenv directives require a path to a specific file. They do not search up the file tree.