From 1e32467f623f08c01f4e3fbec3b1f697a3109811 Mon Sep 17 00:00:00 2001 From: follower Date: Wed, 2 Apr 2014 01:06:45 +1300 Subject: [PATCH] Make `vpc_security_group` docs more accurate Without the `subnet` parameter supplied there's an error `msg: Parameter vpc_security_groups invalid for create command`. (This might be a bug?) If the VPC security group name rather than ID is supplied there's an error: `msg: Invalid security group , groupId= , groupName=.` (Accepting a group name might be a feature enhancement.) In my case I set the subnet as `default` and used `register` to get the result of the security group creation section and just referred to its `group_id` property. --- cloud/rds | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cloud/rds b/cloud/rds index 0e2c8ff2131..525479c0326 100644 --- a/cloud/rds +++ b/cloud/rds @@ -125,7 +125,7 @@ options: aliases: [] vpc_security_groups: description: - - Comma separated list of one or more vpc security groups. Used only when command=create or command=modify. + - Comma separated list of one or more vpc security group ids. Also requires `subnet` to be specified. Used only when command=create or command=modify. required: false default: null aliases: []