aws-samples / aws-samples/codepipeline-nested-cfn

Sub-stack failure propagation

Open
#7 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
269
Forks
284
PR merge metrics
No merged PRs in 30d

Description

If a sub-stack fails to create, is there a way to have the error bubble upwards for capture, or sent somewhere? Currently, if a stack fails to create, the error reason is deleted with the stack during rollback. Kind of hard to troubleshoot unless you are staring at your pipeline.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.