FAQ

Why is there still a CloudFormation stack named mu-bucket-codepipeline after I terminated my pipeline?

The mu-bucket-codepipeline stack contains an S3 bucket for CodePipeline artifacts. It is shared by all pipelines that are deployed in a given region for an account. Therefore, since it is shared, it isn't safe to assume it can be deleted whenever a pipeline is terminated. Additionally, the bucket is likely not empty which would cause an error when CloudFormation tried to delete it. Alternatively, the bucket could have a DeletionPolicy of Retain, but that would cause a conflict the next time pipeline was created and the mu-bucket-codepipeline stack was recreated.

Therefore, the best approach was to retain the CloudFormation stack that managed the bucket. If you would like to delete the stack, then you should first empty the bucket with aws s3 rm s3://mu-codepipeline-<region>-<account_id> --recursive and then deleting the CloudFormation stack.

How can I contribute to mu?

Awesome! Check out the contributing guidelines to get involved.

I still need help. Where can I go to get my question answered?

Ask on Gitter!