Demystifying Terraform 012

Copyright © 2019 HashiCorp
Demystifying
Terraform 0.12

© 2019 HashiCorp 2
Background
• Senior Solutions Engineer
• At Hashicorp for over a year
• Developer/ Consultant/ Sales
background
• Originally from Brazil
• Play once a month in a metal band
@stenio123
stenio@hashicorp.com
Copyright © 2019 HashiCorp ∕ 2

© 2019 HashiCorp 3
Agenda
• Company Overview
• Digital Transformation
• Products Overview
• Terraform 0.12
• Questions/ Discussion

Copyright © 2019 HashiCorp ∕
Company Overview
Founded in 2012 by Mitchell Hashimoto and
Armon Dadgar
Enabling the Cloud Operating Model
Provision, Secure, Connect, and Run any
infrastructure for any application

The Transition
to Multi-Cloud
5

The Transition to Multi-Cloud
Traditional Datacenter
“Static”
Dedicated
Infrastructure
Modern Datacenter
“Dynamic”
AWS Azure GCP+ + +Private Cloud +
“Ticket-based” “Self-service”

“Static”
Dedicated
Infrastructure
Modern Datacenter
“Dynamic”
Why?
• Capex to Opex
• Scale, repeatability, maintainability
• Access to new technologies

“Static”
SYSTEMS OF RECORD SYSTEMS OF ENGAGEMENT
Dedicated
Infrastructure
Modern Datacenter
“Dynamic”

Copyright © 2018 HashiCorp ∕Copyright © 2018 HashiCorp ∕ 9
A Common Operating Model with the
HashiCorp Suite
C++
Provision
Operations
Secure
Security
Run
Development
Connect
Networking
Private Cloud AWS Azure GCP

Product Overview
10

Cloud Provisioning With Terraform
Provision
Operations
Secure
Security
Run
Development
Connect
Networking
A Common Cloud Operating Model

Cloud Provisioning With Terraform
Self-Service provisioning
Templates can be made
available to any development
team for self-provisioning.
Multi-cloud provisioning & compliance
Consistent workflow, API support,
security & policy enforced at provisioning
time.
Infrastructure as Code
Allows repeatability,
scalability, version control and
automation.
Multi-cloud Infrastructure Workflow

Cloud Security With Vault
Provision
Operations
Secure
Security
Run
Development
Connect
Networking

Secret Management With Vault
Dynamic Secrets
Leverage time-bound
credentials or rotate passwords
for databases, cloud platforms
and more.
Encryption as a Service
One workflow to create and
manage keys used to encrypt
your data in-flight and at rest.
Centralized Secrets Management
Securely store, access, and
deploy sensitive information
through a centralized workflow.

Cloud Networking With Consul
Provision
Operations
Secure
Security
Connect
Networking
Run
Development

Multi-Cloud Networking With Consul
Service Segmentation
Secure service-to-service
communication with automatic TLS
encryption and identity-based
authorization.
Service Discovery
Dynamically register and
discover services across
distributed infrastructure.
Runtime Configuration
Feature rich Key/Value store to
easily configure services at scale
and at runtime.
Service Mesh Solution

Cloud Scheduling with Nomad
C++
Provision
Operations
Secure
Security
Run
Development
Connect
Networking

∕Copyright © 2019 HashiCorp 18
Nomad Use Cases
Multi-Cloud Workload Management
Safely manage workloads across
platforms, regions and cloud providers.
Flexible Orchestration
Deploy and manage any
containerized, legacy or batch
application.
Efficient Resource Utilization
Increase resource utilization,
reduce fleet size and cut costs.
Simplified Orchestration

Improving HCL
• First class expressions
• For Expressions
• Generalized “splat” operator
• Conditional improvements
• Dynamic blocks
• Rich Value types
• Improved Template syntax
• Reliable JSON syntax

First Class Expressions
Prior to 0.12, expressions had to be wrapped in interpolation sequences with double quotes, such
as "${var.foo}". With 0.12, expressions are a native part of the language and can be used directly.
Example: ami = var.ami[1]
resource "aws_subnet" "my_subnet" {
vpc_id = aws_vpc.my_vpc.id
cidr_block = "172.16.10.0/24"
tags = {
Name = "tf-0.12-fce-example"
}
}
Example: https://github.com/hashicorp/terraform-guides/blob/master/infrastructure-as-code/terraform-0.12-examples/first-class-expressions/main.tf

For Expressions
For Expression can be used to iterate across multiple items in lists. It does this for several outputs,
illustrating the usefulness and power of the for expression in several ways.
// For expression
output "private_addresses_new" {
value = [
for instance in aws_instance.ubuntu:
instance.private_dns
]
}
Example: https://github.com/hashicorp/terraform-guides/tree/master/infrastructure-as-code/terraform-0.12-examples/for-expressions
// prior to tf 0.12
output "private_addresses_old" {
value = aws_instance.ubuntu.*.private_dns
}
// Equivalent, new splat operator
output "private_addresses_full_splat" {
value = [ aws_instance.ubuntu[*].private_dns ]
}

Generalized “splat” Operator
The splat expression was previously a special-case operation only for attributes on resources with count and didn't
work for any other list values. For Terraform 0.12, we've generalized the operation to work for any list value and are
calling the syntax the "splat operator."
// This is a list without a count associated
output "instance_ip_addrs" {
value = google_compute_instance.example.network_interface.*.address
}

Improvements to Conditional
The conditional operator ... ? ... : ... now supports any value type and lazily evaluates results, as those familiar
with this operator in other languages would expect. Also, the special value null can now be assigned to any field
to represent the absence of a value. This causes Terraform to omit the field from upstream API calls, which is
important in some cases for triggering certain default behaviors.
// This is a list without a count associated
output "ips_with_list_in_brackets" {
value = [
for instance in aws_instance.ubuntu:
(instance.public_ip != "" ? [instance.private_ip, instance.public_ip] : [instance.private_ip])
]
}

Dynamic Blocks
Child blocks such as rule in aws_security_group can now be dynamically generated
based on lists/maps and support iteration.
Example: https://github.com/hashicorp/terraform-guides/tree/master/infrastructure-as-code/terraform-0.12-examples/dynamic-blocks-and-splat-expressions
# Configuration for Terraform 0.11 and earlier
resource "aws_autoscaling_group" "example" {
# ...
tag {
key = "Name"
value = "example-asg-name"
}
tag {
key = "Environment"
value = "production"
}
}
# Configuration for Terraform 0.12
locals {
standard_tags = {
Component = "user-service"
Environment = "production"
}
}
resource "aws_autoscaling_group" "example" {
# ...
tag {
key = "Name"
value = "example-asg-name"
}
dynamic "tag" {
for_each = local.standard_tags
content {
key = tag.key
value = tag.value}
}
}

Rich Value Types
Terraform has supported basic lists and maps as inputs/outputs since Terraform 0.7, but elements were
limited to only simple values. Terraform 0.12 allows arbitrarily complex lists and maps for any inputs and
outputs, including with modules.
Example: https://github.com/hashicorp/terraform-guides/tree/master/infrastructure-as-code/terraform-0.12-examples/rich-value-types
// project/module/output.tf
output "vpc" {
value = aws_vpc.my_vpc
}
output "subnet" {
value = aws_subnet.my_subnet
}
// project/main.tf
output "vpc" {
value = module.network.vpc
}
output "subnet" {
value = module.network.subnet
}
// project/module/output.tf
output "vpc" {
value = aws_vpc.my_vpc
}
output "subnet" {
value = aws_subnet.my_subnet
}
// project/main.tf
output "vpc" {
value = module.network.vpc
}
output "subnet" {
value = module.network.subnet
}
vpc = {
"arn" = "arn:aws:ec2:us-west-2:753646501470:vpc/vpc-
0a1d5a09545df5d29"
"assign_generated_ipv6_cidr_block" = false
"cidr_block" = "172.16.0.0/16"
...
"main_route_table_id" = "rtb-07cbd1dc962def19f"
"owner_id" = "753646501470"
"tags" = {
"Name" = "tf-0.12-rvt-example-vpc"
}
}

Improved Template Syntax
The string interpolation syntax ${ ... } has been part of Terraform since its initial release in 2015. This
continues to work in Terraform 0.12, but is now extended to include support for conditionals
and forexpressions.
Example https://github.com/hashicorp/terraform-guides/tree/master/infrastructure-as-code/terraform-0.12-examples/new-template-syntax
output "just_mary" {
value = <<EOT
%{ for name in var.names ~}
%{ if name == "Mary" }${name}%{ endif ~}
%{ endfor ~}
EOT
}

Reliable JSON Syntax
Terraform 0.12 HCL configuration has an exact 1:1 mapping to and from JSON, providing better error
messages and allowing comments in JSON.
Example https://github.com/hashicorp/terraform-guides/tree/master/infrastructure-as-code/terraform-0.12-examples/reliable-json-syntax
// Using Terraform < 0.12
Error: Error loading /home/ubuntu/test_json/variable1.tf.json: -: "variable" must be followed by a
name
// Using Terraform 0.12
Error: Incorrect JSON value type
on variable1.tf.json line 3, in variable:
3: "example": "foo"
Either a JSON object or a JSON array is required, representing the contents of
one or more "variable" blocks.

Upgrading to Terraform 0.12
Upgrade Guide:
https://www.terraform.io/upgrade-guides/0-12.html
Upgrade tool:
https://www.terraform.io/docs/commands/0.12upgrade.html

Should you Upgrade?
Old stable code - perhaps not necessary
New code – recommended.
If not upgrading, ensure pegging version for Terraform, providers and modules:
terraform {
required_providers {
aws = ">= 2.7.0"
}
}
module "consul" {
source = "hashicorp/consul/aws"
version = "0.0.5"
servers = 3
}
terraform {
required_version = ”< 0.12.0"
}

Demystifying Terraform 012

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Demystifying Terraform 012

Similar to Demystifying Terraform 012 (20)

More from Stenio Ferreira

More from Stenio Ferreira (10)

Recently uploaded

Recently uploaded (20)

Demystifying Terraform 012

Editor's Notes