6b4643fbdc
provider/aws: Increase timeouts for Route Table retries ( #14345 )
2017-05-10 14:41:49 +02:00
db7fe7fe77
provider/aws: Fix panic on nil route configs
...
When creating an `aws_route_table`, if a `route` configuration block is left `nil`, Terraform would previously panic. This allows Terraform to catch a faulty interface conversion during the resource create. The resource will still fail to apply, however, since every item in the `route` element is `Optional` we cannot currently catch this error during plan time, via validation.
Fixes : #13545
2017-04-11 14:45:10 -04:00
7311ba22ea
provider/aws: Add IPv6 Support to aws_route_table ( #12640 )
...
```
% make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSRouteTable_'
==> Checking that code complies with gofmt requirements...
go generate $(go list ./... | grep -v /terraform/vendor/)
2017/03/13 10:11:09 Generated command/internal_plugin_list.go
TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSRouteTable_ -timeout 120m
=== RUN TestAccAWSRouteTable_importBasic
--- PASS: TestAccAWSRouteTable_importBasic (63.14s)
=== RUN TestAccAWSRouteTable_complex
--- PASS: TestAccAWSRouteTable_complex (241.57s)
=== RUN TestAccAWSRouteTable_basic
--- PASS: TestAccAWSRouteTable_basic (91.26s)
=== RUN TestAccAWSRouteTable_instance
--- PASS: TestAccAWSRouteTable_instance (158.18s)
=== RUN TestAccAWSRouteTable_ipv6
--- PASS: TestAccAWSRouteTable_ipv6 (48.99s)
=== RUN TestAccAWSRouteTable_tags
--- PASS: TestAccAWSRouteTable_tags (71.68s)
=== RUN TestAccAWSRouteTable_vpcPeering
--- PASS: TestAccAWSRouteTable_vpcPeering (58.33s)
=== RUN TestAccAWSRouteTable_vgwRoutePropagation
--- PASS: TestAccAWSRouteTable_vgwRoutePropagation (59.64s)
PASS
ok github.com/hashicorp/terraform/builtin/providers/aws 780.400s
```
2017-03-14 12:38:25 +02:00
bb5c83ca49
provider/aws: Increase route_table timeouts ( #8465 )
2016-08-27 21:32:55 +01:00
627efa21f4
provider/aws: Retry RouteTable Route/Assocation creation ( #7156 )
...
* provider/aws: Retry RouteTable Assocation creation
* provider/aws: retry route creation
* remove extra string check
2016-06-14 15:39:52 -05:00
08b7f67227
providers/aws: route table import
2016-05-16 10:03:57 -07:00
0cd0ff0f8e
Use built-in schema.HashString.
2016-02-07 16:29:34 -08:00
47ac10d66b
Change resource.StateChangeConf to use an array for target states
...
Signed-off-by: Ian Duffy <ian@ianduffy.ie>
2016-01-21 01:20:41 +00:00
c519ea74c5
provider/aws: Don't set NatGatewayId with no value
...
This fixes create aws_route_table resources in regions which do not
support the NAT Gateway yet (e.g. eu-central) - unless a value is
explicitly set in which case the API call will fail until such time as
NAT Gateway is supported.
Fixes #4499 .
2016-01-04 16:14:30 -05:00
0bdf249f2c
provider/aws: Add aws_nat_gateway Resource
2015-12-18 14:12:27 -05:00
5c3c1e2327
Merge pull request #3548 from MDL/aws_route
...
provider/aws: add aws_route resource (finish)
2015-10-29 17:06:56 -05:00
44e93526a1
provider/aws: ignore association not exist on route table destroy
...
[GH-3615]
2015-10-23 15:03:54 +02:00
6a593f9d17
Fixing aws identifiers for aws_route.
...
Fixing basic acceptance test.
Adding warning to website about mixed mode.
Adding exists to aws_route.
Adding acceptance test for changing destination_cidr_block.
2015-10-19 09:16:27 -04:00
0c2f189d08
provider/aws: Update to aws-sdk 0.9.0 rc1
2015-08-17 13:27:16 -05:00
f9e825efca
provider/aws: Add new resource - aws_vpc_endpoint
2015-07-14 18:48:41 +01:00
1caef3031b
provider/aws: fix panic when route has no cidr_block
...
While cidr_block is required for static route creation, there are
apparently cases (involving some combination of VPNs, Customer Gateways,
and automatic route propogation) where the cidr_block can come back nil.
This means we cannot assume it's there in the set hash calculation.
2015-06-03 13:43:05 -05:00
b71fa3d0ae
provider/aws: handle upstream aws-sdk-go repo move
...
`awslabs/aws-sdk-go => aws/aws-sdk-go`
Congrats to upstream on the promotion. :)
2015-06-03 13:36:57 -05:00
31258e06c6
provider/aws: fix breakages from awserr refactor
...
This landed in aws-sdk-go yesterday, breaking the AWS provider in many places:
3c259c9586
2015-05-20 06:21:23 -05:00
f7b6b6b2b5
Strip 'sdk' suffix from methods; it's a remnant
2015-05-12 14:58:10 -05:00
5d12c79d90
provider/aws: retry VGW connection a bit due to eventual consistency
2015-05-06 11:09:51 -07:00
f2ddb53c8f
provider/aws: only include network in hash if instance is not set
2015-05-06 10:32:17 -07:00
fb4ac42c65
Merge pull request #1516 from henrikhodne/aws-propagating-vgws
...
provider/aws: add propagating_vgws to route tables
2015-05-05 14:42:45 -07:00
412a2dca0b
Merge pull request #1575 from freshbooks/aws-eni-route
...
provider/aws: Add Elastic Network Interfaces as route destination
2015-05-05 13:28:48 -07:00
fe62312617
Fix comment typos.
2015-04-24 10:25:19 -07:00
769f456028
aws: add propagating_vgws to route tables
2015-04-23 15:03:45 +00:00
e1ac4b9f90
Add Elastic Network Interfaces as route destination
...
Fixes #938
2015-04-17 13:22:31 -04:00
ba43b7c963
mass search-replace of ec2SDKconn
2015-04-16 15:05:55 -05:00
c89470a754
provider/aws: Convert Route table and Route table association to upstream aws-sdk-go
2015-04-10 17:09:36 -05:00
9545f26fa0
Correct AWS VPC or route table read functions
...
If the state file contained a VPC or a route table which no longer
exists, Terraform would fail to create the correct plan, which is to
recreate them.
In the case of VPCs, this was due to incorrect error handling. The AWS
SDK returns a aws.APIError, not a *aws.APIError on error. When the VPC
no longer exists, upon attempting to refresh state Terraform would
simply exit with an error.
For route tables, the provider would recognize that the route table no
longer existed, but would not make the appropriate call to update the
state as such. Thus there'd be no crash, but also no plan to re-create
the route table.
2015-03-20 13:38:41 -04:00
28fbd971fc
Retire goamz
2015-03-13 09:42:50 -05:00
57556bba75
Replace tags files with tags_sdk, rename, and update
2015-03-12 16:43:08 -05:00
3c3b7d51a2
remove duplicated function
2015-03-10 16:52:09 -05:00
30f401eab7
provider/aws: Convert AWS Route Table to aws-sdk-go
2015-03-10 10:23:14 -05:00
44c45994c8
Merge pull request #963 from julienba/master
...
providers/aws: vpc_peering_connection
2015-02-18 06:56:28 -08:00
66f7731995
helper/schema: GetChange shouldn't return true when no change
2015-02-17 15:43:19 -08:00
3b0b41c9a1
allow vpc_peering_connection_id in aws_route_table
2015-02-10 17:50:29 +01:00
54ab857a54
Merge pull request #728 from atlassian/route_diff_fix
...
Route diff fix
2015-01-05 10:43:02 +01:00
66159fd008
ignore routes originating from vgws
2015-01-02 19:17:52 +11:00
f6385215f6
Merge branch 'master' into route_diff_fix
2015-01-02 19:08:53 +11:00
9bdb2fb2d1
This change belongs in a branch
2015-01-02 19:08:33 +11:00
19c6d04928
Do store potentially empty values. Failing to do so will generate different hashes for identical route(s).
2015-01-02 19:03:13 +11:00
639e0c72b4
ignore routes originating from vgws
2014-12-31 10:23:34 +11:00
b595c73d42
Adding tag support to AWS EC2 route table resource.
2014-12-11 00:03:13 +05:30
d3e1a6678d
Making some last tweaks and fixing some acc tests
2014-11-24 21:22:18 +01:00
0725486e89
Refactored the last two resources
2014-11-24 14:04:48 +01:00
eccd5ad308
Refactored about 90%
...
Still need to update 2 resources and check the acceptance tests, but
overall we’re nearly there 😃
2014-11-21 17:58:34 +01:00
9b2b3a963f
ResourceDiff => InstanceDiff
2014-09-17 16:33:24 -07:00
c5d6df692d
providers/aws: tests passing, compiles
2014-09-16 17:49:24 -07:00
f085ae65fa
providers/aws: fix issue where default route was being added
2014-07-12 17:12:41 -07:00
e0bc61d414
providers/aws: route table association tests
2014-07-11 13:10:09 -07:00
Radek Simko