-
Notifications
You must be signed in to change notification settings - Fork 416
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.
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
Modern logs for Serverless Framework v3 #1013
Conversation
Could you also add build specific to Serverless v3? Like the one we have for Serverless v1? |
@j0k3r I'm not sure exactly to what build you're referring. Can you provide more details? |
We have a dedicated build for Serverless v1 (other build use the v2). serverless-webpack/.github/workflows/tests.yml Lines 70 to 99 in 2776bcf
Adding that kind of stuff for Serverless v3, maybe it could interesting to have a build dedicated to that version too. |
Currently, we have just pre-release of v3, but I agree it's good to add it to testing. I've setup dedicated job |
The build using Serverless pre-release is failing. Do you think it's too soon to include it? There is one last change to apply #1013 (comment) and we'll be good to go |
f277364
to
55dde61
Compare
Great thanks for pointing I've missed that. I've fixed it, it was a question of providing some data which in v3 is required by |
Great, just rebase against the master and it'll be good! |
Sure, rebased, thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for all the work 🤝
Oh sh*t. We won't be able to merge because of the coverage drops 🤦♂️ |
@j0k3r FYI we are closing in on the v3 stable release. Not sure how we could help to move this forward, let us know |
Quick update: v3 release is next week |
Thanks @mnapoli. |
Hello @medikoo sorry for being late, the coveralls check is no more required. |
@j0k3r updated! |
Finally 🥳 |
Configure modern logs with provided new logging interface, maintaining compatibility with v2 release of a Framework (this PR ensures no changes to log output happens for that version).
New logs can be tested with
serverless@pre-3
releaseAfter v3 is released, we may consider dropping support for v2, and cleaning up the code so only modern logs are configured - I can help providing a PR
v2 Logs (before)
success:
warning:
error:
v3 Logs (after)
progress:
success:
warning:
error: