From 8d84039aa844e70e7240aab1b16044164428abaf Mon Sep 17 00:00:00 2001 From: vab2048 Date: Thu, 3 May 2018 03:28:08 +0100 Subject: [PATCH] [ec2_vpc_route_table] Use 'network_interface_id' rather than 'interface_id' (#38499) Updated documentation to refer to 'network_interface_id' rather than 'interface_id' as the latter results in an error: 'Parameter validation failed: Unknown parameter in input: \"InterfaceId\"' --- lib/ansible/modules/cloud/amazon/ec2_vpc_route_table.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/ansible/modules/cloud/amazon/ec2_vpc_route_table.py b/lib/ansible/modules/cloud/amazon/ec2_vpc_route_table.py index 94c2c190589..70397cef2d3 100644 --- a/lib/ansible/modules/cloud/amazon/ec2_vpc_route_table.py +++ b/lib/ansible/modules/cloud/amazon/ec2_vpc_route_table.py @@ -57,7 +57,7 @@ options: routes: description: List of routes in the route table. Routes are specified as dicts containing the keys 'dest' and one of 'gateway_id', - 'instance_id', 'interface_id', or 'vpc_peering_connection_id'. + 'instance_id', 'network_interface_id', or 'vpc_peering_connection_id'. If 'gateway_id' is specified, you can refer to the VPC's IGW by using the value 'igw'. Routes are required for present states. state: