Bugfix: Update lambda response processing #258
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #255
Issue: In
invokeHandler
,console.log
was being captured to get string response from lambda invocation, but when being used for manage commands, nothing was actually getting captured byconsole.log
, the JSON parsing of the output would fail since it was parsing an empty string, and the command would always return with 0 status code instead of a 1 as expected for failed commands.This uses the temporary stdout override already in place to capture the return string from the lambda.