@frewilhelm That's not in the controller module. Meaning if I run the task without the root module it doesn't work.

That said, I can't figure out a way for this since Taskfiles doesn't allow nested dotenv. :(

@frewilhelm That's not in the controller module. Meaning if I run the task without the root module it doesn't work.

Maybe we need to move it to the controller then. The envtest version is defined in there as well

Yeah, I'm just going to add something like :

  ENVTEST_K8S_VERSION:
    sh: 'source ../../.env && echo "$ENVTEST_K8S_VERSION"'

this .

instead of

ENVTEST_K8S_VERSION:
    sh: 'source ../../.env && echo "$ENVTEST_K8S_VERSION"'

I think you can use {{ .ROOT_DIR }} so that it will always pick the correct project root on the source

@jakobmoellerdev Root Dir doesn't work if I run the task from under kubernetes/controller. It will try to load the env file from under kubernetes/controller.

➜ task test/e2e/setup/local
source: open /Users/skarlso/goprojects/sap/open-component-model/kubernetes/controller/.env: no such file or directory
task: Command "source /Users/skarlso/goprojects/sap/open-component-model/kubernetes/controller/.env && echo "$KUSTOMIZE_VERSION"" failed: exit status 1

Relative path works whether I run it from root or from the kubernetes/controller folder.

Relative paths are relative, so they break once you change your calling dir. If there is no parent root dir containing env I believe then you should fail or define a fallback value anyhow.

@jakobmoellerdev I'm sorry, I'm not sure what you mean. :D I'm having a brainfart. Do you mean on the values, something like this:

sh: 'test -n "$KIND_NODE_IMAGE_VERSION" && echo "$KIND_NODE_IMAGE_VERSION" || (source ../../.env && echo "$KIND_NODE_IMAGE_VERSION")'

Or do you mean on the ROOT_DIR? And how would ROOT_DIR not exist? Wouldn't it be just . if you launch it from the current folder or something? ROOT_DIR is always the location you are running the task from, isn't it?

@jakobmoellerdev okay, I think this is now okay...?