m1-terraform-provider-helper VS nix-cde

There's virtually no unsolved issue. If you need something x86 is you use rosetta. If you're using terraform and a provider hasn't issued an ARM release you can use the m1 provider helper.

There really isn't any substitute for production experience. Yes you can learn the basics, and the universals are transferable, but you're never going to come across e.g. something like needing this in a homelab, still less the real reasons why you need it...

Try this. https://github.com/kreuzwerker/m1-terraform-provider-helper

tfswitch might help with particular issue of terraform versioning:

https://tfswitch.warrensbox.com/

Even then some versions of terraform providers are not compatible with M1 macs. Docker would help with that probably, but so can: https://github.com/kreuzwerker/m1-terraform-provider-helper

Perhaps these sort of issues support the benefits of per-module docker images?

Check to see if your provider has an M1 compiled version https://github.com/kreuzwerker/m1-terraform-provider-helper/blob/main/docs/provider_information.md

The general availability of darwin_arm64 Terraform providers. There are often cases where the maintainers did not release a darwin_arm64 version yet. Only roughly a fourth of all providers have a darwin_arm64 version released (see here for details)

This is what I'm using with gitlab: https://github.com/takeda/nix-cde/blob/master/contrib/gitlab...

I myself use https://github.com/takeda/nix-cde it just wraps other projects in an opinionated way and contains the boiler plate that I would normally use otherwise.

There's a project that does this with using Nix: https://github.com/takeda/nix-cde (this is a wrapper around https://github.com/nix-community/poetry2nix)

I personally use this: https://github.com/takeda/nix-cde it has the benefit of a reproducible build environment, but unfortunately anything involving Nix has a steep learning curve.

I use this myself: https://github.com/takeda/nix-cde

I don't use NixOS myself, but have Nix installed on my Mac, and it seems to provide all functionality of package or version managers I needed.

I think though it is more complex because it is a programming language that provides this functionality instead of purpose build tool like asdf.

For my needs I created a framework for development: https://github.com/takeda/nix-cde to avoid cruft of including the same things over and over in my projects.

Not an OP, but I became a big fan of using poetry for managing dependencies. For managing python version I started using Nix package manager. It allows to describe all dependencies via code, but with time that code became a boilerplate, so I created this: https://github.com/takeda/nix-cde

It works very well for me so far.