Skip to content

Instantly share code, notes, and snippets.

@brainsik
Last active February 24, 2016 01:32
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save brainsik/106cf7b11a98893a0777 to your computer and use it in GitHub Desktop.
Save brainsik/106cf7b11a98893a0777 to your computer and use it in GitHub Desktop.
Reproducing Terraform GH Issue #5290
$ terraform plan
Refreshing Terraform state prior to plan...
The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed.
Note: You didn't specify an "-out" parameter to save this plan, so when
"apply" is called, Terraform can't guarantee this is what will execute.
+ aws_elb.deafult
availability_zones.#: "" => "<computed>"
connection_draining: "" => "0"
connection_draining_timeout: "" => "300"
dns_name: "" => "<computed>"
health_check.#: "" => "<computed>"
idle_timeout: "" => "60"
instances.#: "" => "<computed>"
internal: "" => "<computed>"
listener.#: "" => "1"
listener.2305901286.instance_port: "" => "12345"
listener.2305901286.instance_protocol: "" => "tcp"
listener.2305901286.lb_port: "" => "12345"
listener.2305901286.lb_protocol: "" => "tcp"
listener.2305901286.ssl_certificate_id: "" => ""
name: "" => "<computed>"
security_groups.#: "" => "<computed>"
source_security_group: "" => "<computed>"
source_security_group_id: "" => "<computed>"
subnets.#: "" => "<computed>"
zone_id: "" => "<computed>"
+ aws_internet_gateway.sandbox
vpc_id: "" => "${aws_vpc.default.id}"
+ aws_security_group.blue
description: "" => "Managed by Terraform"
egress.#: "" => "<computed>"
ingress.#: "" => "<computed>"
name: "" => "<computed>"
owner_id: "" => "<computed>"
vpc_id: "" => "${aws_vpc.default.id}"
+ aws_subnet.default
availability_zone: "" => "us-east-1a"
cidr_block: "" => "192.168.0.0/20"
map_public_ip_on_launch: "" => "0"
vpc_id: "" => "${aws_vpc.default.id}"
+ aws_vpc.default
cidr_block: "" => "192.168.0.0/16"
default_network_acl_id: "" => "<computed>"
default_security_group_id: "" => "<computed>"
dhcp_options_id: "" => "<computed>"
enable_classiclink: "" => "<computed>"
enable_dns_hostnames: "" => "<computed>"
enable_dns_support: "" => "<computed>"
main_route_table_id: "" => "<computed>"
Plan: 5 to add, 0 to change, 0 to destroy.
$ terraform apply
aws_vpc.default: Creating...
cidr_block: "" => "192.168.0.0/16"
default_network_acl_id: "" => "<computed>"
default_security_group_id: "" => "<computed>"
dhcp_options_id: "" => "<computed>"
enable_classiclink: "" => "<computed>"
enable_dns_hostnames: "" => "<computed>"
enable_dns_support: "" => "<computed>"
main_route_table_id: "" => "<computed>"
aws_vpc.default: Creation complete
aws_subnet.default: Creating...
availability_zone: "" => "us-east-1a"
cidr_block: "" => "192.168.0.0/20"
map_public_ip_on_launch: "" => "0"
vpc_id: "" => "vpc-92bf9af6"
aws_internet_gateway.sandbox: Creating...
vpc_id: "" => "vpc-92bf9af6"
aws_security_group.blue: Creating...
description: "" => "Managed by Terraform"
egress.#: "" => "<computed>"
ingress.#: "" => "<computed>"
name: "" => "<computed>"
owner_id: "" => "<computed>"
vpc_id: "" => "vpc-92bf9af6"
aws_subnet.default: Creation complete
aws_internet_gateway.sandbox: Creation complete
aws_security_group.blue: Creation complete
aws_elb.deafult: Creating...
availability_zones.#: "" => "<computed>"
connection_draining: "" => "0"
connection_draining_timeout: "" => "300"
dns_name: "" => "<computed>"
health_check.#: "" => "<computed>"
idle_timeout: "" => "60"
instances.#: "" => "<computed>"
internal: "" => "<computed>"
listener.#: "" => "1"
listener.2305901286.instance_port: "" => "12345"
listener.2305901286.instance_protocol: "" => "tcp"
listener.2305901286.lb_port: "" => "12345"
listener.2305901286.lb_protocol: "" => "tcp"
listener.2305901286.ssl_certificate_id: "" => ""
name: "" => "<computed>"
security_groups.#: "" => "1"
security_groups.2236446470: "" => "sg-b90bd8c1"
source_security_group: "" => "<computed>"
source_security_group_id: "" => "<computed>"
subnets.#: "" => "1"
subnets.1110652908: "" => "subnet-35a17d1f"
zone_id: "" => "<computed>"
aws_elb.deafult: Creation complete
Apply complete! Resources: 5 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.
State path: terraform.tfstate
$ perl -i -pe 's/security_groups/#security_groups/' main.tf
$ grep security_groups main.tf
#security_groups = ["${aws_security_group.blue.id}"]
$ terraform plan
Refreshing Terraform state prior to plan...
aws_vpc.default: Refreshing state... (ID: vpc-92bf9af6)
aws_security_group.blue: Refreshing state... (ID: sg-b90bd8c1)
aws_subnet.default: Refreshing state... (ID: subnet-35a17d1f)
aws_internet_gateway.sandbox: Refreshing state... (ID: igw-8a8423ee)
aws_elb.deafult: Refreshing state... (ID: tf-lb-cofhdjxd3vbhpbrdfxhnxo4dg4)
No changes. Infrastructure is up-to-date. This means that Terraform
could not detect any differences between your configuration and
the real physical resources that exist. As a result, Terraform
doesn't need to do anything.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment