Skip to content

How to send 'Reason' field when using CloudFormation Custom resource #1801

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.

Sign up for GitHub

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

Jump to bottom
Closed
phipag opened this issue Mar 13, 2025 · 5 comments · Fixed by #1758 or #1810
Closed

How to send 'Reason' field when using CloudFormation Custom resource #1801

phipag opened this issue Mar 13, 2025 · 5 comments · Fixed by #1758 or #1810
Assignees
@phipag
Labels
custom-resources feature-request New feature or request

Comments

@phipag
Copy link
Contributor

phipag commented Mar 13, 2025

Discussed in #1742

Originally posted by rahuldeverani September 29, 2024
Hi team , I am following this doc: https://docs.powertools.aws.dev/lambda/java/utilities/custom_resources/#customising-a-response , to customise custom resource response.

I want my CloudFormation stack to show why the custom resource failed. For that we can send 'Reason' in the CloudFormation response : https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/crpg-ref-responses.html

How to send this 'Reason' using lambda powertool custom resource implementation ?
@phipag phipag added the feature-request New feature or request label Mar 13, 2025
@phipag phipag self-assigned this Mar 13, 2025
@phipag phipag moved this from Triage to Working on it in Powertools for AWS Lambda (Java) Mar 13, 2025
@phipag
Copy link
Contributor Author

phipag commented Mar 13, 2025

Hi @rahuldeverani,

Pull request #1758 was created by @moizsh regarding this issue. This PR introduces the reason field in the Powertools custom resource Response class.

I will look into merging this PR soon and will notify you here once it is merged.

@phipag phipag linked a pull request Mar 13, 2025 that will close this issue
feat(cfn-custom-resource): Add optional 'reason' field for detailed failure reporting #1758
Merged
6 tasks
@phipag phipag mentioned this issue Mar 13, 2025
Merged
6 tasks
@phipag
Copy link
Contributor Author

phipag commented Mar 21, 2025

Merged PR #1758. Next steps: Merge same changes to v2 branch to avoid diverging features.

@phipag phipag reopened this Mar 21, 2025
@phipag phipag mentioned this issue Mar 24, 2025
Merged
@phipag phipag linked a pull request Mar 24, 2025 that will close this issue
feat(cfn-custom-resource): Add optional 'reason' field for detailed failure reporting #1810
Merged
@phipag
Copy link
Contributor Author

phipag commented Mar 24, 2025

Created PR for v2 branch: #1810

@phipag phipag moved this from Working on it to Coming soon in Powertools for AWS Lambda (Java) Mar 24, 2025
@phipag phipag closed this as completed Mar 24, 2025
@phipag
Copy link
Contributor Author

phipag commented Mar 24, 2025

Merged.

@phipag
Copy link
Contributor Author

phipag commented Mar 24, 2025

This feature will be released in the upcoming release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@phipag phipag

Labels
custom-resources feature-request New feature or request
Projects
Powertools for AWS Lambda (Java)
Status: Coming soon
Milestone
No milestone
1 participant
@phipag