The Direnv usage + Terraform shim code was thrown together very quickly.
Some ideas:
Make .jinjaformrc a requirement
Allow creating .jinaformrc with a command
jinjaform create (don't conflict with terraform init)
Look for .jinjaformrc file in the current or parent directories - when it is found, that is the project root.
If someone wants different configs for different directories then perhaps a LOOK_UP (name to be determined) command could be used to continue searching up the tree for the project root.
Look for terraform in $PATH that is not jinjaform itself. That is the terraform binary to run, rather than specifying it with an environment variable.
Remove Direnv specific code from Jinjaform and start using the following in .envrc files:
The Direnv usage + Terraform shim code was thrown together very quickly.
Some ideas:
.jinjaformrca requirement.jinaformrcwith a commandjinjaform create(don't conflict withterraform init).jinjaformrcfile in the current or parent directories - when it is found, that is the project root.LOOK_UP(name to be determined) command could be used to continue searching up the tree for the project root.terraformin$PATHthat is not jinjaform itself. That is the terraform binary to run, rather than specifying it with an environment variable..envrcfiles: