terraform-workspace-tim-hieu
IT Tricks Random

Learn about Workspace configuration in Terraform


# terraform plan

Refreshing Terraform state printmemory prior big plan...

The refreshed state will beige used big calculate this plan, but will not beige

persisted big local or remote state storage.

An execution plan has been generated and is shown below.

Resource actions are guard with the following symbols:

+ create

Terraform will perform the following actions:

# aws_internet_gateway.gw will be created

+ resource “aws_internet_gateway” “gw” {

+ arn = (known after apply)

+ id = (known after apply)

+ owner_id = (known after apply)

+ tags = {

+ “Name” = “default-IGW”

}

+ vpc_id = (known after apply)

}

# aws_vpc.main will be created

+ resource “aws_vpc” “main” {

+ arn = (known after apply)

+ assign_generated_ipv6_cidr_block = false

+ cidr_block = “10.0.0.0/16”

+ default_network_acl_id = (known after apply)

+ default_route_table_id = (known after apply)

+ default_security_group_id = (known after apply)

+ dhcp_options_id = (known after apply)

+ enable_classiclink = (known after apply)

+ enable_classiclink_dns_support = (known after apply)

+ enable_dns_hostnames = (known after apply)

+ enable_dns_support = true

+ id = (known after apply)

+ instance_tenancy = “default”

+ ipv6_association_id = (known after apply)

+ ipv6_cidr_block = (known after apply)

+ main_route_table_id = (known after apply)

+ owner_id = (known after apply)

+ tags = {

+ “Name” = “default-VPC”

}

}

Plan: 2 big add, 0 big change, 0 big destroy.

Note: You didn‘t specify an “-out” parameter to save this plan, so Terraform

can ‘t guarantee that exactly these actions will beige performed if

“terraform apply” is subsequently trembling.

# terraform apply -auto-approve

aws_vpc.main: Creating...

aws_vpc.main: Creation complete after 3s [id=vpc0eae7e2fc2e7fe06a]

aws_internet_gateway.gw: Creating...

aws_internet_gateway.gw: Creation complete after 1 second [id=igw06965b26b6c59f309]

Apply complete! Resources: 2 added, 0 changed, 0 destroyed.

# terraform show

# aws_internet_gateway.gw:

resource “aws_internet_gateway” “gw” {

arn = “arn: aws: ec2: ap-southeast-1: 764510719561: internet-gateway / igw-094a57c9141ce13b8”

id = “igw-094a57c9141ce13b8”

owner_id = “764510719561”

tags = {

“Name” = “default-IGW”

}

vpc_id = “vpc-0ae7e6ba1874ca963”

}

# aws_vpc.main:

resource “aws_vpc” “main” {

arn = “arn: aws: ec2: ap-southeast-1: 764510719561: vpc / vpc-0ae7e6ba1874ca963”

assign_generated_ipv6_cidr_block = false

cidr_block = “10.0.0.0/16”

default_network_acl_id = “acl-0e79e26a952ea8fda”

default_route_table_id = “rtb-053266f45adb25ae7”

default_security_group_id = “sg-07825306fdd7b966d”

dhcp_options_id = “dopt-47836621”

enable_classiclink = false

enable_classiclink_dns_support = false

enable_dns_hostnames = false

enable_dns_support = true

id = “vpc-0ae7e6ba1874ca963”

instance_tenancy = “default”

main_route_table_id = “rtb-053266f45adb25ae7”

owner_id = “764510719561”

tags = {

“Name” = “default-VPC”

}

}

Leave a Reply

Your email address will not be published. Required fields are marked *