Difference between revisions of "Terraform"
| Line 11: | Line 11: | ||
A high-level difference and/or reason to use Terraform over Ansible, Chef, Puppet, Saltstack, etc., is that these others have a focus on automating the installation and configuration of software (i.e., keeping the machines in compliance and in a certain state). Terraform, however, can automate provisioning of the infrastructure itself (e.g., in AWS or Google). One can, of course, do the same with, say, Ansible. However, Terraform really shines in infrastructure management and automation. | A high-level difference and/or reason to use Terraform over Ansible, Chef, Puppet, Saltstack, etc., is that these others have a focus on automating the installation and configuration of software (i.e., keeping the machines in compliance and in a certain state). Terraform, however, can automate provisioning of the infrastructure itself (e.g., in AWS or Google). One can, of course, do the same with, say, Ansible. However, Terraform really shines in infrastructure management and automation. | ||
| + | |||
| + | ==Bash completion== | ||
| + | |||
| + | $ cat << EOF >> /etc/bash_completion.d/terraform | ||
| + | _terraform() | ||
| + | { | ||
| + | local cmds cur colonprefixes | ||
| + | cmds="apply destroy fmt get graph import init \ | ||
| + | output plan push refresh remote show taint \ | ||
| + | untaint validate version state" | ||
| + | |||
| + | COMPREPLY=() | ||
| + | cur=${COMP_WORDS[COMP_CWORD]} | ||
| + | # Work-around bash_completion issue where bash interprets a colon | ||
| + | # as a separator. | ||
| + | # Work-around borrowed from the darcs work-around for the same | ||
| + | # issue. | ||
| + | colonprefixes=${cur%"${cur##*:}"} | ||
| + | COMPREPLY=( $(compgen -W '$cmds' -- $cur)) | ||
| + | local i=${#COMPREPLY[*]} | ||
| + | while [ $((--i)) -ge 0 ]; do | ||
| + | COMPREPLY[$i]=${COMPREPLY[$i]#"$colonprefixes"} | ||
| + | done | ||
| + | |||
| + | return 0 | ||
| + | } && | ||
| + | complete -F _terraform terraform | ||
| + | EOF | ||
| + | </pre> | ||
==External links== | ==External links== | ||
Revision as of 22:43, 5 January 2017
Terraform is a tool for building, changing, and versioning infrastructure safely and efficiently. Terraform can manage existing and popular service providers as well as custom in-house solutions. It is a popular tool in DevOps.
Introduction
- Infrastructure as Code
- Used for the automation of your infrastructure
- It keeps your infrastructure in a certain state (compliant)
- E.g., 2 web instances and 2 volumes and 1 load balancer
- It makes your infrastructure auditable
- That is, you can keep your infrastructure change history in a version control system (e.g., git)
A high-level difference and/or reason to use Terraform over Ansible, Chef, Puppet, Saltstack, etc., is that these others have a focus on automating the installation and configuration of software (i.e., keeping the machines in compliance and in a certain state). Terraform, however, can automate provisioning of the infrastructure itself (e.g., in AWS or Google). One can, of course, do the same with, say, Ansible. However, Terraform really shines in infrastructure management and automation.
Bash completion
$ cat << EOF >> /etc/bash_completion.d/terraform
_terraform() {
local cmds cur colonprefixes
cmds="apply destroy fmt get graph import init \
output plan push refresh remote show taint \
untaint validate version state"
COMPREPLY=()
cur=${COMP_WORDS[COMP_CWORD]}
# Work-around bash_completion issue where bash interprets a colon
# as a separator.
# Work-around borrowed from the darcs work-around for the same
# issue.
colonprefixes=${cur%"${cur##*:}"}
COMPREPLY=( $(compgen -W '$cmds' -- $cur))
local i=${#COMPREPLY[*]}
while [ $((--i)) -ge 0 ]; do
COMPREPLY[$i]=${COMPREPLY[$i]#"$colonprefixes"}
done
return 0
} && complete -F _terraform terraform EOF </pre>
