Kristin Laemmert mildwonkey

Terraform v0.13

Terraform v0.13 introduces a new provider source attribute that allows you to declare the registry source of a terraform provider. This attribute is part of the required_providers setting inside a terraform configuration block.

The Registry currently indexes Official and Partner providers, and later work will allow for community providers as well, which Terraform will automatically download and install on terraform init.

Background

Provider Installation

Overview

Terraform 0.13 has an entirely new provider installer that allows for greater control over individual provider installation methods. The breaking change is a new, required, subdirectory hierarchy for provider binaries.

Terraform v0.12

Terraform v0.12 Provider Installer

The key differences between Terraform v0.12 and v0.13 are the directory hierarchy. Terraform v0.12 would look for a provider binary under the following directories:

Provider Source Usage Examples

Config with no changes required

Example:

# with no provider configuration at all, terraform will identify this by the 
# it's resource type "aws" and assume that the user meant "hashicorp/aws" 
resource "aws_instance" {
  # resource config
}

Keybase proof

I hereby claim:

I am mildwonkey on github.
I am mildwonkey (https://keybase.io/mildwonkey) on keybase.
I have a public key whose fingerprint is 4B87 B457 75C8 8B34 55A1 B2CE 2EAA 6271 014E ABF9

To claim this, I am signing this object:

	provider "aws" {
	region = "us-east-1"
	}

	variable "rsa_public_key_file" {
	type = string
	}

	resource "aws_key_pair" "key" {
	key_name = "terraform-test"