Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
What do you want us to build?
If an App Runner deployment fails because of a health check, it doesn't automatically fail the CloudFormation deployment. This leaves the Stack in a drifted state because App Runner will rollback its configurations but not inform CloudFormation of that rollback.
This is also particularly annoying because in a CodePipeline this won't block subsequent deployments since CloudFormation doesn't know there's an issue with the current image. Custom tests won't help here because there's no way to test against the failing App Runner image.
Community Note
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
What do you want us to build?
If an App Runner deployment fails because of a health check, it doesn't automatically fail the CloudFormation deployment. This leaves the Stack in a drifted state because App Runner will rollback its configurations but not inform CloudFormation of that rollback.
This is also particularly annoying because in a CodePipeline this won't block subsequent deployments since CloudFormation doesn't know there's an issue with the current image. Custom tests won't help here because there's no way to test against the failing App Runner image.