Skip to content

Latest commit

 

History

History
66 lines (44 loc) · 3.65 KB

README.md

File metadata and controls

66 lines (44 loc) · 3.65 KB
Raw

docker-asdf-terraform-ci-base

build_and_test

A minimal Docker image based on Ubuntu 20.04 for use in Terraform/Terragrunt/Terratest CI pipelines. The image contains alls dependencies for installing Terraform and related tools using asdf. The following items can be installed (all dependencies are met, but they are not installed, so you can control the versions):

Python3 is installed at the system level since we assume that the version of Python is irrelevant, as long as it's installed.

Use

Images are built in Github Actions and hosted at hub.docker.com/r/percygrunwald/docker-asdf-terraform-ci-base.

docker pull percygrunwald/docker-asdf-terraform-ci-base

Docker tags

Each image has the following tags, which allow you to specify a specific release:

  • vYYYY-MM-DD-HHMMSS - the main release tag, composed of the date/time of the build
  • git-$COMMIT_HASH - the commit hash of the commit in this repository from which the image was built
  • ubuntu-$DOCKER_DIGEST - the short digest of the underlying Ubuntu docker image

In CI/CD pipelines

A suggested workflow

  • Use percygrunwald/docker-asdf-terraform-ci-base as the base image for the CI pipeline
  • Install asdf with git clone and run asdf install to install all tools (terraform, terragrunt, golang, etc.)
  • Run CI tasks (lint, test, terraform plan, etc.)
  • Cache ~/.asdf directory for future runs (hash based on .tool-versions file)

CI/CD for this repo

This repo is a "live" repo. It "follows" the ubuntu repo on Docker Hub and when a new version of the 20.04 (Focal) base image is released, Github Actions will update the Dockerfile, build and test the resulting image, commit the changes, push the new image to Docker Hub and create a Github release. Please see the .github for full details.

Testing the CI/CD pipeline locally

You can test the CI/CD pipeline (Github Actions) locally using nektos/act. Requires docker.

--reuse reuses the containers for each workflow job, keeping all installed tools/dependencies. This is recommended for frequent runs since act cannot make use of actions caching, which means all tools/dependencies must be downloaded each time. If you ever want to start again from scratch (empty container), just run without --reuse.

# Install act with go (see act docs for other installation options)
go install github.com/nektos/act@latest

Run the push workflow, DOCKER_PASSWORD should be set to an access token and passed as a secret:

act push --reuse

export DOCKER_PASSWORD=...
act workflow_dispatch --reuse -s DOCKER_PASSWORD
act schedule --reuse -s DOCKER_PASSWORD