Support injecting dotenv environment variables into tasks

[croth1]

Problem description

pixi tasks nicely support environment variables. Being able to inject environment variables from a .env file could make it easy for injecting host-specific environment variables into pixi run <task-name> without having to manually source the .env file first.

I will leave this here for voting. It's a nice-to-have for me - maybe somebody else would also find this useful for their workflow?

[bollwyvl]

I've been using generated .env's as outputs to isolate/generate settings in the absence of a solid matrix mechanism.

If .env is supported, seems like it would need a fair amount of specificity to handle the breadth of ways it is used, ideally providing a way to compose in a predictable order with other configuration:

[tasks.build]
cmd = "whatever"
env = {FOO="bar"}
env-file = ".env"
# or
env-file = [".env", ".env.dev"]
# and maybe
depends-on = [
  { task="preflight", environment="build", env={FOO="$FOO"}, env-file=[".env.another"] }
]

[croth1]

@bollwyvl, interesting, to be honest I haven't thought about how deep this needs to go - just a weekend observation 😬 Would be one env file per environment enough for your use case? Behaviour like:

By default all environments will source .env. Beyond that allow overwriting this behaviour by setting one per environment, like:

[environments.test]
features = ["test"]
env-file = ".test.env"

(config example is not an implementation suggestion, just for conveying the concept)

[bollwyvl]

Merely pointing to the flexibility afforder by e.g. task.

As usual: whatever it does, just needs to do that thing consistently.