> The most popular tool in HashiCorp's ecosystem that wasn't written by them was written by a consulting firm who hated HashiCorp's UX
Which tool is that?
On a related note, Vault has a really excellent API. A joy.
Which tool is that?
On a related note, Vault has a really excellent API. A joy.
Strongly disagree: suppose we have secrets mounted at my/secrets, and we want to read a secret top/secret, which is represented as my/secrets/top/secret path in vault. However, the only way to access it via API is to read _all_ mount points, and match them with the path to split path to mount point and secret. vault cli itself follows the same logic: https://github.com/hashicorp/vault/blob/main/command/kv_help...
Second that. Very steep learning curve for some use cases that could be accomplished in a much easier way. Another kubernetes in disguise.
This is the initial comment about Terragrunt, which doesn't say that
Used right it's the only way to remain sane on any non-trivial set of infra where you don't end up hand-rolling a half-baked version of Terragrunt.
Getting to this point was a learning process though. Probably six solid years of investment now.
I second that Terraform needs to work at least on dynamically specifying providerblocks. This is where people usually resort to terragrunt.
Workspaces and state layering are in my experience hard on the novices and unfortunately they turn to terragrunt.