asdf-hashicorp VS asdf

brew install asdf asdf plugin-add terraform https://github.com/asdf-community/asdf-hashicorp.git asdf install terraform 0.12 asdf exec terraform destroy

I'm a huge fan of asdf and have been using for years together with direnv! It's great to see how much effort is put into it! I hope more people adopt it so that we don't have to `curl | sh`! One thing I have issues with asdf is security as are no checksums, so, you if I project get compromised you'll get compromised, too. This, of course, is in addition to the third-party asdf plugin getting itself compromised (which is the greater risk). Last, but not least - I wish asdf came with something like eget [0] incorporated so that it can install 99% of the plugins directly and safely! Last, but not least - 99% of the plugins have almost identical code and all that changes is the repo, so, this should be generalized. For example, many years ago I made just one codebase of all HashiCorp plugins [1] and it's been working great!

[0]: https://github.com/zyedidia/eget

[1]: https://github.com/asdf-community/asdf-hashicorp

CMD> asdf plugin list all Output sample: [...] kubebuilder https://github.com/virtualstaticvoid/asdf-kubebuilder.git kube-capacity https://github.com/looztra/asdf-kube-capacity.git kubectl *https://github.com/Banno/asdf-kubectl.git kubectl-bindrole https://github.com/looztra/asdf-kubectl-bindrole.git kubectx *https://gitlab.com/wt0f/asdf-kubectx.git kubefedctl https://github.com/kvokka/asdf-kubefedctl.git kubeseal https://github.com/stefansedich/asdf-kubeseal.git kubesec https://github.com/vitalis/asdf-kubesec.git kubespy https://github.com/jfreeland/asdf-kubespy.git kubeval https://github.com/stefansedich/asdf-kubeval.git terraform *https://github.com/Banno/asdf-hashicorp.git terraform-docs *https://github.com/looztra/asdf-terraform-docs.git terraform-lsp https://github.com/bartlomiejdanek/terraform-lsp.git terraform-validator https://github.com/looztra/asdf-terraform-validator.git terragrunt https://github.com/lotia/asdf-terragrunt.git [...]

I've been using it and has contributed to it, but I wish it supported out of the box GitHub-based release binaries as 90% of my code for different vendors was relatively the same, so, instead of having multiple identical repositories, I created one, which uses introspection [0].

I wish this was available out of the box to handle literary 90% of the tools.

Also, I typically pair it with direnv [1] for even more magic.

[0]: https://github.com/Banno/asdf-hashicorp

[1]: https://direnv.net/

Or if you need to manage more than just node, asdf has been around for over a decade and works great. You can use a .tool-versions to change runtimes for each project you have, in addition to managing your global runtime versions

https://asdf-vm.com/

Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?

These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…

We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).

(asdf)[https://asdf-vm.com/] fully supports Python and almost any other language. I've been using it for Ruby, Python, Elixir, and other languages for years and never looked back.

Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).

There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:

I've really been enjoying asdf, which is a program that allows you to install specified versions of dev utilities as well as dynamically manage them via shims and .tool-versions files.

I use the asdf version manager.