Is there no way to have stacks created by the pipeline deleted when the pipeline stack is deleted?

[lestephane]

This is a question, not an issue per se.

i note this statement:

Note: While removing the resources, delete the Prod & UAT stacks created by pipeline before deleting the pipeline since those CloudFormations stacks uses the role created by pipeline stack.

I've experienced the pain of having to remove stacks in the right order.

When developing a pipeline you need to repeatedly create and delete the outlying codepipeline stack, and are left to delete the sub-stacks. It would be nice if there was a way to have stacks created by the pipeline be deleted when the pipeline gets deleted (in reverse dependency order).

Is there a way to do this, or does the user have to remember to delete the stacks created by the pipeline manually everytime, in the right order? Any advice is welcome.

[mmahmood]

Facing the same issue. Any solution will greatly help.

[elelkhoury]

Still having the same issue, I had to go and create a custom CloudFormation stack based on lambda to delete the stack as part of the template in Service Catalogue. It's such a workaround but does the trick. This was possible since my pipeline is created through Service Catalogue and I manage the object dependency from within alongside the Custom resource to clean up the stack triggered by the pipeline