Lifecycle Event Handlers - Add Error Logging #4391
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.
Changes
With this PR, we've added basic error logging during the execution of lifecycle event handlers.
This will help users debug issues because, not only will they be able to see the newly added logs in their CloudWatch, but also, in their browser.
The following example shows a log that happened because of an error that occurred in a

onEntryBeforePublish
lifecycle event:Note
In case you missed it, with the
DEBUG
env variable set totrue
, all of the logs that happened during a single API HTTP requests are actually forwarded to user's console.Note
The
DEBUG
env variable is usually used with dev and pre-prod Webiny instances.How Has This Been Tested?
Manually.
Documentation
Changelog.