Request

• Bug
• New Feature
• Refactor
• Question
• Documentation
• Tests
• Other

Details

• Would be great to figure out some magic to add template validation testing in CircleCI
• Maybe a Rakefile task?

The documentation indicates

If you discover bugs while in Production, you can revert to previous application version by clicking and approving the change again.

Does this imply you need to revert code and re-commit to have the pipeline build again, or is there a way to simply flip the blue/green deployments back to the previous version. The later would be preferable. In this case would a

The module outputs the param codebuild_badge_url (as documented in the Outputs section of README) but seems like there is no input variable called badge_enabled. Seems like a simple fix and would be greatly appreciated if this could be added. Thanks

The IAM policy for the role allows * too too many aws services without resource restrictions. Allowing a var supplied policy here could be a good first step. (https://github.com/cloudposse/terraform-aws-ecs-codepipeline/blame/master/main.tf#L66-L87).

IMHO you can use Makefile to organize the vars changes and big commands (if you add terraform inside docker commands)

Can somebody please clean up the CloudFormation in this file:

https://github.com/ModusCreateOrg/capsule/blob/master/ci/s3_cloudformation.cf

We need a RegEx adding to ensure the project name is valid for use in an S3 bucket. Currently, there is no validation on the name as per the description:

Description: "Name of the project. TODO: Add validation regex"