Add CAPABILITY_NAMED_IAM to cloudformation capabilities

While from the documentation[1] one would assume that replacing
CAPABILITY_IAM with CAPABILITY_NAMED_IAM; this as empirically been shown
to not be the case.

1: "If you have IAM resources, you can specify either capability. If you
have IAM resources with custom names, you must specify
CAPABILITY_NAMED_IAM."
http://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html
This commit is contained in:
Matthew Martin 2016-07-21 10:54:40 -05:00 committed by Matt Clay
parent 3818cc2b95
commit 4d952d6e6e

View file

@ -329,7 +329,7 @@ def main():
stack_policy_body=stack_policy_body,
template_url=template_url,
disable_rollback=disable_rollback,
capabilities=['CAPABILITY_IAM'],
capabilities=['CAPABILITY_IAM', 'CAPABILITY_NAMED_IAM'],
**kwargs)
operation = 'CREATE'
except Exception as err:
@ -352,7 +352,7 @@ def main():
stack_policy_body=stack_policy_body,
disable_rollback=disable_rollback,
template_url=template_url,
capabilities=['CAPABILITY_IAM'])
capabilities=['CAPABILITY_IAM', 'CAPABILITY_NAMED_IAM'])
operation = 'UPDATE'
except Exception as err:
error_msg = boto_exception(err)