Skip to content
Visit Terraform on GitHub
Set theme to dark (⇧+D)

Tracking your history

In the first step of the tutorial, you created and applied some basic Cloudflare configuration. Terraform was able to apply this configuration to your account because you provided your email address and API token at the top of the file:

$ head -n4 cloudflare.tfprovider "cloudflare" {  email = ""  token = "your-api-key"}

In this step of the tutorial, we’re going to store your configuration in GitHub where it can be tracked, peer-reviewed, and rolled back to as needed. But before we do so, we're going to remove your credentials from the Terraform config file so it doesn't get committed to a repository.

1. Using Environment Variables for Authentication

As a good security practice we need to remove your Cloudflare credentials from anything that will be committed to a repository. The Cloudflare Terraform provider supports reading these values from the CLOUDFLARE_EMAIL and CLOUDFLARE_TOKEN environment variables, so all we need to do is:

$ sed -ie 's/^.*email =.*$/  # email pulled from $CLOUDFLARE_EMAIL/'$ sed -ie 's/^.*token =.*$/  # token pulled from $CLOUDFLARE_TOKEN/'
$ head -n4 cloudflare.tfprovider "cloudflare" {  # email pulled from $CLOUDFLARE_EMAIL  # token pulled from $CLOUDFLARE_TOKEN}
$ export$ export CLOUDFLARE_TOKEN=your-api-key

Note that you need to leave the empty provider definition in the file, so that Terraform knows to install the Cloudflare plugin. In a future tutorial, we'll discuss some of the more advanced options that can be used with the provider.

After completing the above step, it's a good idea to make sure that you can still authenticate to Cloudflare. By running terraform plan we can get Terraform to pull the current state (which requires a valid email and API key):

$ terraform planRefreshing Terraform state in-memory prior to plan...The refreshed state will be used to calculate this plan, but will not bepersisted to local or remote state storage.
cloudflare_record.www: Refreshing state... (ID: c38d3102767284e7ca14d5dad3ab8b69)
No changes. Infrastructure is up-to-date.
This means that Terraform did not detect any differences between yourconfiguration and real physical resources that exist. As a result, noactions need to be performed.

2. Storing Configuration in GitHub

Now that credentials have been removed, it's time to initialize a git repository with your Cloudflare configuration and then push it to GitHub.

First we'll create the GitHub repository to store the config. This can be done via the GitHub UI or with a simple API call:

$ export GITHUB_USER=your-github-user$ export GITHUB_TOKEN=your-github-token
$ export GITHUB_URL=$(curl -sSXPOST$GITHUB_TOKEN -H 'Content-Type: application/json' \-d '{"name": "cf-config", "private":"true"}' 2>/dev/null | jq -r .ssh_url)
$ echo $$GITHUB_USER/cf-config.git

Now we'll initialize a git repository and make our first commit:

$ git initInitialized empty Git repository in /Users/username/cf-config/.git/
$ git remote add origin $GITHUB_URL$ git add
$ git commit -m "Step 2 - Initial commit with webserver definition."[master (root-commit) 5acea17] Step 2 - Initial commit with webserver definition. 1 file changed, 16 insertions(+) create mode 100644

An astute reader may have noticed that we did not commit the .terraform directory nor did we commit the terraform.tfstate file. The former was not committed because this repository may be used on a different architecture, and the plugins contained in this directory are built for the system on which terraform init was run. The latter was not committed as i) it may eventually contain sensitive strings and ii) it is not a good way to keep state in sync, as explained in Sharing State.

To prevent git from bugging us about these files, let's add them to a new .gitignore file, commit it, and push everything to GitHub:

$ cat > .gitignore <<'EOF'.terraform/terraform.tfstate*EOF
$ git add .gitignore
$ git commit -m "Step 2 - Ignore terraform plugin directory and state file."[master 494c6d6] Step 2 - Ignore terraform plugin directory and state file. 1 file changed, 2 insertions(+) create mode 100644 .gitignore
$ git pushCounting objects: 6, done.Delta compression using up to 8 threads.Compressing objects: 100% (4/4), done.Writing objects: 100% (6/6), 762 bytes | 0 bytes/s, done.Total 6 (delta 0), reused 0 (delta 0)To$GITHUB_USER/cf-config.git * [new branch]      master -> master