Zoltán Reegn

> Having to create a provider just so I can have, eg, a function that refactors a complicated loop that is specific to a given module, is totally not practical...

I don't mind the specific terminology used. Can be `head` and `tail`, or `first` and `rest` or even `firstItem` vs `remainingItems` (although this one would diverge most from existing naming...

BTW original issue I've opened was #2260 this was just a quick run at the problem, I don't mind how it's solved.

Would be great to have some sort of local caching for OCI charts instead of this ephemeral in-memory solution we have today. The workflow with OCI lacking caching is much...

That's as expected, as both provide the same executable. You should uninstall (or at least unlink) terraform, and install tfenv, and set a default version (with `tfenv use 1.4.1`) I...

As to why go through all this trouble: because historically terraform sucked when it comes to backward-compatibility, so anyone using it should be pinning the terraform version they are using....

That's because hashicorp didn't publish any binaries for M1 macs before 1.0.2. The same problem applies to using older provider versions. If you need to use earlier terraform (or provider...

Yeah, I poked around that bash logic last week and indeed it seems to be flaky.

> it's just not been released to homebrew It just not been released *period*. It's not homebrew-s fault that there's no tfenv release of that feature. If tfenv has a...

@txomon The same argument would be true for kubectl. Should kubectl not have KUBECONFIG support either? Your argument would also apply to KUBE_CONFIG_PATH environment variable support as well. I don't...