Barry Kaplan

I am finding dotenv essentially useless. If an env was defined when executing task, there seems to be no way to use dotenv to override the value. LIke @mjftw, I...

Even trying to fork a new task carries with it all the env ``` build: desc: Pre argo/kustomize build dir: "{{.ROOT_DIR}}" cmd: task _build _build: # same as what build...

And I can't even raise an error if run from the wrong directory ``` build: desc: Pre argo/kustomize build preconditions: - msg: "Must run build from root dir {{.ROOT_DIR}}" sh:...

strike that, this does it ``` build: desc: Pre argo/kustomize build preconditions: - msg: "Must run build from root dir {{.ROOT_DIR}}" sh: '[ "{{.USER_WORKING_DIR}}" = "{{.ROOT_DIR}}" ]' cmds: - echo...

This is a real smell in the design. Seems like a technical solution that was not fully mapped to the use cases. I guess for now we need to duplicate...

Its interesting that most (all?) examples of using hooks for work that requires credentials, the credentials are hard coded in the hook manifest. Thereby sidestepping the issue being discussed here....