Skip to content

Instantly share code, notes, and snippets.

@bensojona
Created April 9, 2015 23:00
Show Gist options
  • Save bensojona/5bc7e1e8be560a901494 to your computer and use it in GitHub Desktop.
Save bensojona/5bc7e1e8be560a901494 to your computer and use it in GitHub Desktop.
Refreshing Terraform state prior to plan...
aws_key_pair.consul: Refreshing state... (ID: consul-key)
aws_security_group.allow_all: Refreshing state... (ID: sg-54bdc030)
module.consul.aws_instance.consul.0: Refreshing state... (ID: i-8a47e177)
module.consul.aws_instance.consul.1: Refreshing state... (ID: i-bd46e040)
module.consul.aws_instance.consul.2: Refreshing state... (ID: i-3f46e0c2)
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_security_group.allow_all
ingress.532441254.cidr_blocks.#: "0" => "1"
ingress.532441254.cidr_blocks.0: "" => "0.0.0.0/0"
ingress.532441254.from_port: "" => "0"
ingress.532441254.protocol: "" => "-1"
ingress.532441254.security_groups.#: "0" => "0"
ingress.532441254.self: "" => "0"
ingress.532441254.to_port: "" => "65535"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment