Skip to content
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

Ability to set "Reason" in failure cases #6

Open
rclark opened this issue Oct 2, 2018 · 0 comments · May be fixed by #11
Open

Ability to set "Reason" in failure cases #6

rclark opened this issue Oct 2, 2018 · 0 comments · May be fixed by #11

Comments

@rclark
Copy link

rclark commented Oct 2, 2018

cfn-response/index.js

Line 15 in 97f2629

Reason: "See the details in CloudWatch Log Stream: " + context.logStreamName,

There should be a mechanism for the caller to provide failure details if the invocation of the Lambda function failed. This would allow the the user to read CloudFormation event logs in order to understand what actions they should take in order to remedy the problem.
ndchelsea added a commit to ndchelsea/cfn-response that referenced this issue Feb 7, 2020
@ndchelsea
improvements to interface
dd8a943 
- allow Reason to be passed in parameters (resolves LukeMizuhashi#6)
- allow callback to be passed in parameters, allowing one to easily use
  promises rather than needing to pass a custom context object
  to ensure resolve/reject is called
@ndchelsea ndchelsea linked a pull request Feb 7, 2020 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

improvements to interface ndchelsea/cfn-response
1 participant
@rclark