After #369 we now introduce a logger implementation on the frontend side that leverages the /logs endpoint implemented in the previous PR.
It is possible to use the newly introduced logger to push log entries to the backend in async, so they end up in CloudWatch lambda log streams.
Changes
How Has This Been Tested?
unit tests
manual tests checking the backend gets the message and logs correctly
PR Quality Checklist
[x] I added tests to new or existing code
[ ] I removed hardcoded strings and used our i18n solution instead (see here)
[x] I made sure no sensitive info gets logged at any time in the codebase (see here) (e.g. no user info or details, no stacktraces, etc.)
[ ] I checked that infrastructure/update_infrastructure.sh runs without any error
[x] I checked that npm run build builds without any error
[ ] I checked that clusters are listed correctly
[ ] I checked that a new cluster can be created (config is produced and dry run passes)
[ ] I checked that login and logout work as expected
Description
After #369 we now introduce a logger implementation on the frontend side that leverages the /logs endpoint implemented in the previous PR. It is possible to use the newly introduced logger to push log entries to the backend in async, so they end up in CloudWatch lambda log streams.
Changes
How Has This Been Tested?
PR Quality Checklist
i18nsolution instead (see here)npm run buildbuilds without any errorIn order to increase the likelihood of your contribution being accepted, please make sure you have read both the Contributing Guidelines and the Project Guidelines
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.