ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

provider/aws: retry VGW connection a bit due to eventual consistency

This commit is contained in:
Mitchell Hashimoto 2015-05-06 11:09:51 -07:00
parent f2ddb53c8f
commit 5d12c79d90
1 changed files with 20 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
builtin/providers/aws/resource_aws_route_table.go
View File

@ -210,11 +210,26 @@ func resourceAwsRouteTableUpdate(d *schema.ResourceData, meta interface{}) error
for _, vgw := range add {
id := vgw.(string)
log.Printf("[INFO] Enabling VGW propagation for %s: %s", d.Id(), id)
_, err := conn.EnableVGWRoutePropagation(&ec2.EnableVGWRoutePropagationInput{
RouteTableID: aws.String(d.Id()),
GatewayID: aws.String(id),
})
var err error
for i := 0; i < 5; i++ {
log.Printf("[INFO] Enabling VGW propagation for %s: %s", d.Id(), id)
_, err = conn.EnableVGWRoutePropagation(&ec2.EnableVGWRoutePropagationInput{
RouteTableID: aws.String(d.Id()),
GatewayID: aws.String(id),
})
if err == nil {
break
}
// If we get a Gateway.NotAttached, it is usually some
// eventually consistency stuff. So we have to just wait a
// bit...
ec2err, ok := err.(aws.APIError)
if ok && ec2err.Code == "Gateway.NotAttached" {
time.Sleep(20 * time.Second)
continue
}
}
if err != nil {
return err
}