Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adds support to run cf templates with CAPABILITY_NAMED_IAM #50

Merged

Conversation

ntmggr
Copy link
Contributor

@ntmggr ntmggr commented Nov 3, 2017

Needed if you want to create IAM with custom named resources. Resolves the CF error Requires capabilities : [CAPABILITY_NAMED_IAM]

@santiagocardenas
Copy link
Contributor

This must be a per execution option.

It's normally not advised to use custom names IAM resources for reusable CloudFormation templates. This is because it causes collisions if they are deployed more than once in the same account.

Of course, there are cases where custom named resources are used and make sense, but not for the majority of use cases where taskcat would be involved in.

@tonynv
Copy link
Contributor

tonynv commented Feb 7, 2018

Will make this an option on the CLI in a later commit

@tonynv tonynv merged commit d0d6b1e into aws-ia:develop Feb 7, 2018
andrew-glenn pushed a commit that referenced this pull request Oct 29, 2019
Enable CLI and Wire up (linting, lambda_builds, s3staging, validate, stack creation, display_progress, stack deletion)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants