This repository aims to provide a helpful set of structural guidelines to follow when working with Terraform, as well giving a basic enablement with the tool through a series of simple demos.

What is Terraform? Have a read here!

How can I install Terraform on my machine? Get it here!

The end state of this Terraform repository will have the ability to deploy compute and networking infrastructure into the following cloud providers:

• AWS
• Microsoft Azure
• Google Cloud Platform

Networking infrastructure will contain:

• VPCs
• Subnets (public & private)
• Routing Tables
• NAT Gateways
• Internet Gateways
• Security Groups
• Elastic Load Balancers

Compute infrastructure will contain:

• EC2 instances (AWS)
• Azure instances (Microsoft Azure)
• Google compute instances (Google Cloud Platform)

Terraform provisioning will contain examples of:

• Puppet configuration management
• Chef configuration management
• Ansible configuration management

Terraform code for the above code is to be released incrementally in parts, accompanied by a blog. The releases will be split as follows:

• Release 1: Directory Structure and Basic Compute in AWS (Find the demo here)
• Release 2: Basic Compute in Microsoft Azure & Google Cloud Platform (Find the demos here and here respectively)
• Release 3: Networking Infrastructure
• Release 4: Terraform Provisioning with Puppet, Chef & Ansible

Each release will also be accompanied with a series of demos relating to the new functionality.

## The Commands

These are the commands that will be at the core of every demo contained in this repository:

• terraform get
• terraform plan
• terraform apply
• terraform destroy

Before progressing into any demos, it is also very important to understand 'state' in the context of Terraform, how it is fits in and the criticality of state file management.

Each directory level will have a explanation of how the sub-directories are all structured, what is contained in them and why they should be set out this way.

This is the base of the Terraform repository, inclusive of sub-directories that are named after the cloud providers that you wish to deploy into using Terraform.