TGF

A Terragrunt frontend that allow execution of Terragrunt/Terraform through Docker.

Table of content:

Description
Configuration
Invocation arguments
Images
Usage
Development

Description

TGF is a small utility used to launch a Docker image and automatically map the current folder, your HOME folder and your current environment variables to the underlying container.

By default, TGF is used as a frontend for terragrunt, but it could also be used to run different endpoints.

Why use TGF

Using TGF ensure that all your users are using the same set of tools to run infrastructure configuration even if they are working on different environments (linux, Microsoft Windows, Mac OSX, etc).

Terraform is very sensible to the version used and if one user update to a newer version, the state files will be marked with the latest version and all other user will have to update their Terraform version to the latest used one.

Also, tools such as AWS CLI are updated on a regular basis and people don't tend to update their version regularly, resulting in many different version among your users. If someone make a script calling a new feature of the AWS api, that script may break when executed by another user that has an outdated version.

Installation

Choose the desired version according to your OS here, unzip it, make tgf executable chmod +x tgf and put it somewhere in your PATH.

or install it through command line:

On OSX:

curl -sL https://github.com/coveo/tgf/releases/download/v1.16.5/tgf_1.16.5_macOS_64-bits.zip | bsdtar -xf- -C /usr/local/bin

On Linux:

curl -sL https://github.com/coveo/tgf/releases/download/v1.16.5/tgf_1.16.5_linux_64-bits.zip | gzip -d > /usr/local/bin/tgf && chmod +x /usr/local/bin/tgf

On Windows with Powershell:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Invoke-WebRequest https://github.com/coveo/tgf/releases/download/v1.16.5/tgf_1.16.5_windows_64-bits.zip -OutFile tgf.zip

Configuration

TGF looks for a file named .tgf.config or tgf.user.config in the current working folder (and recursively in any parent folders) to get its parameters. If some parameters are missing, it tries to find the remaining configuration through the AWS parameter store under /default/tgf using your current AWS CLI configuration if any.

Your configuration file could be expressed in any of the YAML, JSON or Terraform HCL declarative language.

Example of YAML configuration file:

docker-refresh: 1h
logging-level: notice

Example of HCL configuration file:

docker-refresh = "1h"
logging-level = "notice"

Example of JSON configuration file:

"docker-refresh": "1h"
"logging-level": "notice"

Configuration keys

Key	Description	Default value
docker-image	Identify the docker image to use	coveo/tgf
docker-image-version	Identify the image version
docker-image-tag	Identify the image tag (could specify specialized version such as k8s, full)	latest
docker-image-build	List of Dockerfile instructions to customize the specified docker image)
docker-image-build-folder	Folder where the docker build command should be executed
docker-refresh	Delay before checking if a newer version of the docker image is available	1h (1 hour)
docker-options	Additional options to supply to the Docker command
logging-level	Terragrunt logging level (only apply to Terragrunt entry point). Critical (0), Error (1), Warning (2), Notice (3), Info (4), Debug (5), Full (6)	Notice
entry-point	The program that will be automatically launched when the docker starts	terragrunt
tgf-recommended-version	The minimal tgf version recommended in your context (should not be placed in `.tgf.config file`)	no default
recommended-image	The tgf image recommended in your context (should not be placed in `.tgf.config file`)	no default
environment	Allows temporary addition of environment variables	no default
run-before	Script that is executed before the actual command	no default
run-after	Script that is executed after the actual command	no default

Note: The key names are not case sensitive

Configuration section

It is possible to specify configuration elements that only apply on specific os.

Example of HCL configuration file:

docker-refresh: 1h
logging-level: notice
windows:
  logging-level: debug
linux:
  docker-refresh: 2h

section	Description
windows	Configuration that is applied only on Windows systems
linux	Configuration that is applied only on Linux systems
darwin	Configuration that is applied only on OSX systems
ix	Configuration that is applied only on Linux or OSX systems

TGF Invocation

> tgf
usage: tgf [<flags>]

DESCRIPTION: TGF (terragrunt frontend) is a Docker frontend for terragrunt/terraform. It automatically maps your current folder, your HOME folder, your TEMP folder as well of most environment variables to the docker process. You can add -D to your command to get the exact docker command that is generated.

It then looks in your current folder and all its parents to find a file named '.tgf.config' to retrieve the default configuration. If not all configurable values are satisfied and you have an AWS configuration, it will then try to retrieve the missing elements from the AWS Parameter Store under the key '/default/tgf'.

Configurable values are: docker-image, docker-image-version, docker-image-tag, docker-image-build, docker-image-build-folder, docker-refresh, docker-options, recommended-image-version, required-image-version, logging-level, entry-point, tgf-recommended-version.

You can get the full documentation at https://github.com/coveo/tgf/blob/master/README.md and check for new version at https://github.com/coveo/tgf/releases/latest.

Any docker image could be used, but TGF specialized images could be found at: https://hub.docker.com/r/coveo/tgf/tags.

Terragrunt documentation could be found at https://github.com/coveo/terragrunt/blob/master/README.md (Coveo fork) or https://github.com/gruntwork-io/terragrunt/blob/master/README.md (Gruntwork.io original)

Terraform documentation could be found at https://www.terraform.io/docs/index.html.

IMPORTANT: Most of the tgf command line arguments are in uppercase to avoid potential conflict with the underlying command. If any of the tgf arguments conflicts with an argument of the desired entry point, you must place that argument after -- to ensure that they are not interpreted by tgf and are passed to the entry point. Any non
conflicting argument will be passed to the entry point wherever it is located on the invocation arguments.

  tgf ls -- -D   # Avoid -D to be interpretated by tgf as --debug-docker

VERSION: 1.16.5

AUTHOR: Coveo

Flags:
  -H, --tgf-help                 Show context-sensitive help (also try --help-man).
  -D, --debug-docker             Print the docker command issued
  -F, --flush-cache              Invoke terragrunt with --terragrunt-update-source to flush the cache
      --refresh-image            Force a refresh of the docker image (alias --ri)
      --get-image-name           Just return the resulting image name (alias --gi)
      --no-home                  Disable the mapping of the home directory (alias --nh)
      --no-temp                  Disable the mapping of the temp directory (alias --nt)
      --mount-point=MOUNT-POINT  Specify a mount point for the current folder --mp)
      --docker-arg=<opt> ...     Supply extra argument to Docker (alias --da)
      --all-versions             Get versions of TGF & all others underlying utilities (alias --av)
      --current-version          Get current version infomation (alias --cv)
  -E, --entrypoint=terragrunt    Override the entry point for docker
      --image=coveo/tgf          Use the specified image instead of the default one
      --image-version=version    Use a different version of docker image instead of the default one (alias --iv)
  -T, --tag=latest               Use a different tag of docker image instead of the default one
  -P, --profile=""               Set the AWS profile configuration to use
  -L, --logging-level=<level>    Set the logging level (critical=0, error=1, warning=2, notice=3, info=4, debug=5, full=6)

Example:

> tgf --current-version
tgf v1.16.5

Returns the current version of the tgf tool

> tgf -- --version
terragrunt version v0.12.24.10(Coveo)

Returns the version of the default entry point (i.e. Terragrunt), the --version located after the -- instructs tgf to pass this argument to the desired entry point

> tgf -E terraform -- --version
Terraform v0.9.11

Returns the version of Terraform since we specified the entry point to be terraform.

Default Docker images

Base image: coveo/tgf.base (based on Alpine)

Terraform
Terragrunt
Go Template
Shells & tools
- sh
- openssl

Default image: coveo/tgf (based on Alpine)

All tools included in coveo/tgf:base plus:

Python (2 and 3)
Ruby
AWS CLI
jq
Terraforming
Tflint
Terraform-docs
Terraform Quantum Provider
Shells
- bash
- zsh
- fish
Tools & editors
- vim
- nano
- zip
- git
- mercurial

AWS provider specialized image: coveo/tgf:aws (based on Alpine)

All tools included in coveo/tgf plus:

terraform-provider-aws (fork)

Kubernetes tools (based on Alpine)

All tools included in coveo/tgf:aws plus:

kubectl
kops
helm

Full image: coveo/tgf:full (based on Ubuntu)

All tools included in the other images plus:

AWS Tools for Powershell
Oh My ZSH
Shells
- powershell

Usage

As Terragrunt front-end

> tgf plan

Invoke terragrunt plan (which will invoke terraform plan) after doing the terragrunt relative configurations.

> tgf apply -var env=dev

Invoke terragrunt apply (which will invoke terraform apply) after doing the terragrunt relative configurations. You can pass any arguments that are supported by terraform.

> tgf plan-all

Invoke terragrunt plan-all (which will invoke terraform plan on the current folder and all sub folders). Terragrunt allows xxx-all operations to be executed according to dependencies that are defined by the dependencies statements.

Other usages

> tgf -e aws s3 ls

Invoke AWS CLI as entry point and list all s3 buckets

> tgf -e fish

Start a shell fish in the current folder

> tgf -t full -e powershell

Starts a powershell in the current working directory.

> tgf -e my_command -i my_image:latest

Invokes my_command in your own docker image. As you can see, you can do whatever you need to with tgf. It is not restricted to only the pre-packaged Docker images, you can use it to run any program in any Docker images. Your imagination is your limit.

Development

Build are automatically launched on tagging.

Tags with format image-0.0.0 automatically launch a Docker images build that are available through Docker Hub. Tags with format v0.0.0 automatically launch a new release on Github for the TGF executable.

sryabkov/tgf

TGF