catalin/moto
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Allow boto3 redshift cluster subnet group creation

Browse source 
Boto3 deviates from the AWS docs in the way subnets are described when
creating a Redshift cluster subnet group.

This entry in botocore nests the SubnetIds under SubnetIdentifier tags:
https://github.com/boto/botocore/blob/develop/botocore/data/redshift/2012-12-01/service-2.json#L5423-L5429
referenced here:
https://github.com/boto/botocore/blob/develop/botocore/data/redshift/2012-12-01/service-2.json#L2296

And the AWS docs do not nest them that way:
https://docs.aws.amazon.com/redshift/latest/APIReference/API_CreateClusterSubnetGroup.html

Fixes #1029
This commit is contained in:
Jack Danger 2017-08-02 11:45:27 -07:00
commit 5011cd28b6
2 changed files with 34 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
moto/redshift/responses.py
View file

@ -122,6 +122,10 @@ class RedshiftResponse(BaseResponse):
cluster_subnet_group_name = self._get_param('ClusterSubnetGroupName')
description = self._get_param('Description')
subnet_ids = self._get_multi_param('SubnetIds.member')
# There's a bug in boto3 where the subnet ids are not passed
# according to the AWS documentation
if not subnet_ids:
subnet_ids = self._get_multi_param('SubnetIds.SubnetIdentifier')
subnet_group = self.redshift_backend.create_cluster_subnet_group(
cluster_subnet_group_name=cluster_subnet_group_name,