Slides and sample code from my talk "Infrastructure As Code - Muss man nicht testen, Hauptsache es läuft" on tech&talk at 25th June 2024.

All code samples are in samples.

There are three samples chapter, one for Ansible, Docker and Helm Charts.

The code samples samples/ansible are tested with Ansible Core 2.17.0 and Vagrant 2.4.1.

Following test tools are used:

• Ansible-lint 24.5.1
• Testinfra 10.1.0

I prepare some Vagrantfiles for the setup of the test infrastructure if necessary. The only prerequires are that you have to install VirtualBox and Vagrant on your machine. Then follow these steps:

1. Open a CLI and go to the location of the file Vagrantfile.
2. Call vagrant up. Vagrant will download the necessary image for VirtualBox. That will take some times.

Hint: Public and private keys can be generated with the following command: ssh-keygen

Ansible playbook samples are in samples. This is also the location for the next CLI calls.

• Code quality check for Ansible playbooks with Ansible-lint: ansible-lint *.yml
• Running ansible playbooks against the test infrasructure (see chapter 'Setup Test Infrastructure' above):

ansible-playbook -i inventory/test setup-tomcat.yml

• Running testinfra tests against a provisioned VM:

py.test --connection=ansible --ansible-inventory inventory/test -v tests/*.py

The code samples samples/docker are tested with Docker 21.0.1.

Following test tools are used:

• Haskell Dockerfile Linter (hadolint) 2.12.0
• Container Structure Test 1.18.1

cd samples/docker
hadolint Dockerfile

cd samples/docker

docker build -t sparsick/spring-boot-demo:latest .
container-structure-test test --image sparsick/spring-boot-demo:latest --config spring-boot-test.yaml

The code samples samples/helm-charts are tested with Helm Chart 3.15.1 and Minikube 1.33.1 (uses Kubernetes 1.30.0)

Following test tools are used:

• terratest 0.46.15

cd samples/helm-charts
minikube start --addons=ingress
helm upgrade -i spring-boot-demo-instance spring-boot-demo -f local-values.yaml

Call minikube ip to find out the IP address of your Minikube cluster and add it in your /etc/hosts

// /etc/hosts
192.168.49.2    spring-boot-demo.local

then you can see the application in your browser with http://spring-boot-demo.local/hero

cd samples/helm-charts
helm lint spring-boot-demo -f local-values.yaml

The tests are located in samples/helm-charts/spring-boot-demo/templates/tests. If you want to run the test, you need a running minikube

cd samples/helm-charts
helm test spring-boot-demo-instance

The tests are located in samples/helm-charts/test. If you want to run the test, you need a running minikube and Golang on your machine.

cd samples/helm-charts/test
go mod tidy
go test . -v

The code samples samples/terraform are tested with Terraform 1.7.4 and Cloud Provider 'Azure'.

Following test tools are used:

• TFLint 0.48.0
• terratest 0.46.15

You need an account at Azure and you log in with Azure CLI.

TFLint is used as linter. For Azure we need to install a special TFLint Plugin for Azure. The plugin is configured in the tflint config file samples/terraform/azure-demo/.tflint.hcl. Then you can run the linter with following commands:

cd samples/terraform/azure-demo
tflint --init
TFLINT_LOG=info tflint 

The tests are located in samples/terraform/test. If you want to run the test, you Golang on your machine and you are log in Azure via Azure CLI.

cd samples/terraform/test
go mod tidy
go test . -v