-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cfn-custom-resource): Add optional 'reason' field for detailed failure reporting #1758
feat(cfn-custom-resource): Add optional 'reason' field for detailed failure reporting #1758
Conversation
…ailure reporting in CloudFormation custom resource responses
|
I created issue #1801 related to this PR. |
Thanks @moizsh for your contribution. This change looks good to me and the PR is ready to be merged. |
Actually the Java 8 build fails. I'll look into this. The build fails with
But it succeeds locally using Java 8 and the same gradle version. |
Testing if bumping the Kotlin example version to the current one ( Anyway, this issue is not related to this PR and can be investigated separately. |
This resolved the issue, we have an open issue to improve the existing workflows (#1231). |
|
Issue #, if available:
#1801
Description of changes:
This PR adds an optional 'reason' field to the CloudFormation Custom Resource response model. This enhancement allows users to provide detailed failure reasons for Custom Resource creation/update operations, particularly useful in scenarios where the Lambda function is hosted in a separate account and logs are not directly accessible. The 'reason' field enables better error reporting and debugging for consumers of the Custom Resource.
Checklist
Breaking change checklist
RFC issue #: N/A
Changes made:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.