asdf-python VS terraform

Point of clarification: asdf uses python-build which is from pyenv.

https://github.com/asdf-community/asdf-python?tab=readme-ov-...

[env] # supports arbitrary env vars so mise can be used like direnv/dotenv NODE_ENV = 'production' [tools] # specify single or multiple versions terraform = '1.0.0' erlang = ['23.3', '24.0'] # supports everything you can do with .tool-versions currently node = ['16', 'prefix:20', 'ref:master', 'path:~/.nodes/14'] # send arbitrary options to the plugin, passed as: # MISE_TOOL_OPTS\_\_VENV=.venv python = {version='3.10', virtualenv='.venv'} [plugins] # specify a custom repo url # note this will only be used if the plugin does not already exist python = 'https://github.com/asdf-community/asdf-python' [alias.node] # project-local aliases my_custom_node = '20'

Yeah, I should've been more precise. The asdf plugins use parts of existing systems. For example (python/ruby/node)-build which mostly come from other version managers. Asdf does provide extras, but the plugin-specific code is tiny: https://github.com/asdf-community/asdf-python/blob/master/bi...

❯ asdf plugin-list --urls --refs act https://github.com/grimoh/asdf-act.git master 8729029 aws-vault https://github.com/beardix/asdf-aws-vault.git master 937a1db awscli https://github.com/MetricMike/asdf-awscli.git main b9ba4c7 docker-slim https://github.com/everpeace/asdf-docker-slim.git master 4ee75a3 golang https://github.com/kennyp/asdf-golang.git master 1f388f1 helm https://github.com/Antiarchitect/asdf-helm.git master 87eef5a java https://github.com/halcyon/asdf-java.git master f0c702f jq https://github.com/ryodocx/asdf-jq.git master 3144577 kubectl https://github.com/asdf-community/asdf-kubectl.git master da7bb0b minikube https://github.com/alvarobp/asdf-minikube.git master 8ca7b8d mysql https://github.com/iroddis/asdf-mysql.git master 3aaf756 nodejs https://github.com/asdf-vm/asdf-nodejs.git master cb61e3d perl https://github.com/ouest/asdf-perl.git master 31bb799 php https://github.com/asdf-community/asdf-php.git master 759843b postgres https://github.com/smashedtoatoms/asdf-postgres.git master 4f8b356 python https://github.com/danhper/asdf-python.git master 8ab052f redis https://github.com/smashedtoatoms/asdf-redis.git master bf1276e ruby https://github.com/asdf-vm/asdf-ruby.git master f134c2d sbt https://github.com/bram2000/asdf-sbt.git master 33f9637 scala https://github.com/asdf-community/asdf-scala.git master 1206055 skaffold https://github.com/virtualstaticvoid/asdf-skaffold.git master c942ecf spark https://github.com/joshuaballoch/asdf-spark.git master 6fe49de

You could look at what a new $PATH file looks like by spinning up a new VM or google around for default path examples. As for your dependency issues, I like to use poetry and asdf to keep things straight.

I use asdf and its Python plugin [1] to install Python interpreter versions.

For managing virtual environments on my preferred shell (Fish), I use (and maintain) VirtualFish [2].

For managing project dependencies, I activate environments via VirtualFish and then use Poetry [3] to update the dependencies within the environments.

[1]: https://github.com/danhper/asdf-python

[2]: http://github.com/justinmayer/virtualfish

[3]: http://python-poetry.org

The terraform test command and the options of mocking resources and data sources enable a lot more than we have tried out here in this blog post. I highly recommend to take a closer look at the documentation and the blog post referenced before and play around with them. Be aware that this is a quite "young" functionality, so maybe you stumble over issues or might miss some features. If this is the case you definitely should open an issue in the corresponding repository.

I decided to use Terraform to manage my K8 resources. I know that there are probably better ways of doing this (like Argo CD or Flux CD), but I ended up settling with Terraform as I was already familiar with the tool and it allowed me to achieve the goal of trying out K8s without being bogged down too much on the deployment process.

It uses HashiCorp Terraform to provision the PKI and secrets so that they can be quickly and easily rotated.

I used the aws console at first to get reacquainted with dynamodb, lambda and apigateway. After getting everything to work, I used Terraform to deploy all of the infrastructure pieces. The Github repo can be found here.

Rather than point and click in the AWS console, I decided to start with IaC using Terraform. I also decided to use GitHub actions(https://docs.github.com/en/actions) for CI/CD to get familiar with them. I had only used GitLab CI/CD and runners previously, which are very similar to GitHub Actions.

To implement this, we need to create a pair of EC2 instances along with their corresponding resources, such as roles and security groups, in our AWS account. Doing this manually for every EC2 instance type we need to measure could be tedious, so we'll use Terraform for this task.

Dan: The entire deployment workflow for Kubernetes revolves around Argo CD. When I set up a cluster, some might default to using kubectl apply, or if they're using Terraform, they might opt for the Helm provider to install various Helm charts. However, with Argo CD, I have precise control over deployment processes.

Terraform/OpenTofu installed. We use Terraform in this article.

First and foremost, I embarked on replicating the existing infrastructure on Digital Ocean using Infrastructure as Code (IaC) principles, specifically leveraging tools like Terraform to automate the setup process.