· 7 years ago · May 21, 2018, 08:06 PM
1âž” ls -lah
2total 48
3drwxr-xr-x 8 alxgol staff 272B 23 окт 00:25 .
4drwxr-xr-x 263 alxgol staff 8,7K 23 окт 00:09 ..
5-rw-r--r-- 1 alxgol staff 271B 18 окт 15:51 aws_provider.tf
6-rw-r--r-- 1 alxgol staff 125B 23 окт 00:24 gateway.tf
7-rw-r--r-- 1 alxgol staff 193B 23 окт 00:24 route-table-association.tf
8-rw-r--r-- 1 alxgol staff 229B 23 окт 00:24 route-table.tf
9-rw-r--r-- 1 alxgol staff 262B 23 окт 00:24 subnet.tf
10-rw-r--r-- 1 alxgol staff 97B 23 окт 00:25 vpc.tf
11
12âž” terraform plan
13var.access_key_id
14 Enter a value: access-key
15
16var.region
17 Enter a value: eu-west-2
18
19var.secret_access_key
20 Enter a value: secret-key
21
22Refreshing Terraform state in-memory prior to plan...
23The refreshed state will be used to calculate this plan, but will not be
24persisted to local or remote state storage.
25
26The Terraform execution plan has been generated and is shown below.
27Resources are shown in alphabetical order for quick scanning. Green resources
28will be created (or destroyed and then created if an existing resource
29exists), yellow resources are being changed in-place, and red resources
30will be destroyed. Cyan entries are data sources to be read.
31
32Note: You didn't specify an "-out" parameter to save this plan, so when
33"apply" is called, Terraform can't guarantee this is what will execute.
34
35+ aws_internet_gateway.gateway-jetruby
36 tags.%: "1"
37 tags.Name: "Intenet Gateway"
38 vpc_id: "${aws_vpc.vpc-jetruby.id}"
39
40+ aws_route_table.route-table-jetruby
41 route.#: "1"
42 route.~222644434.cidr_block: "0.0.0.0/0"
43 route.~222644434.egress_only_gateway_id: ""
44 route.~222644434.gateway_id: "${aws_internet_gateway.gateway-jetruby.id}"
45 route.~222644434.instance_id: ""
46 route.~222644434.ipv6_cidr_block: ""
47 route.~222644434.nat_gateway_id: ""
48 route.~222644434.network_interface_id: ""
49 route.~222644434.vpc_peering_connection_id: ""
50 tags.%: "1"
51 tags.Name: "Route Table"
52 vpc_id: "${aws_vpc.vpc-jetruby.id}"
53
54+ aws_route_table_association.route-table-association-jetruby
55 route_table_id: "${aws_route_table.route-table-jetruby.id}"
56 subnet_id: "${aws_subnet.subnet-jetruby.id}"
57
58+ aws_subnet.subnet-jetruby
59 assign_ipv6_address_on_creation: "false"
60 availability_zone: "<computed>"
61 cidr_block: "10.0.0.0/16"
62 ipv6_cidr_block: "<computed>"
63 ipv6_cidr_block_association_id: "<computed>"
64 map_public_ip_on_launch: "true"
65 tags.%: "1"
66 tags.Name: "Subnet"
67 vpc_id: "${aws_vpc.vpc-jetruby.id}"
68
69+ aws_vpc.vpc-jetruby
70 assign_generated_ipv6_cidr_block: "false"
71 cidr_block: "10.0.0.0/16"
72 default_network_acl_id: "<computed>"
73 default_route_table_id: "<computed>"
74 default_security_group_id: "<computed>"
75 dhcp_options_id: "<computed>"
76 enable_classiclink: "<computed>"
77 enable_dns_hostnames: "<computed>"
78 enable_dns_support: "true"
79 instance_tenancy: "<computed>"
80 ipv6_association_id: "<computed>"
81 ipv6_cidr_block: "<computed>"
82 main_route_table_id: "<computed>"
83 tags.%: "1"
84 tags.Name: "VPC"
85
86
87Plan: 5 to add, 0 to change, 0 to destroy.