CI friendly logging

[vicary]

Is your feature request related to a problem? Please describe.
The deploy timer is nice when working with normal shells, but CI logs, or outputs piped to a file in general does not play nice with the /r line replacement.

Describe the solution you'd like
I would like the deployment script to either expose a CLI option (e.g. --ci), or read a commonly used environment variable CI=true.

Describe alternatives you've considered
None exists, we have to manually scroll through 10k lines if it ends up with errors.

Additional context

[dphang]

Yes I've seen this too, but assumed this was an issue from the Serverless Framework, not this component, not sure we can do anything about it unless we change how we deploy or use new Serverless component version. @danielcondemarin any ideas?

[danielcondemarin]

Yes I've seen this too, but assumed this was an issue from the Serverless Framework, not this component, not sure we can do anything about it unless we change how we deploy or use new Serverless component version. @danielcondemarin any ideas?

Right now I don't think there is anything we can do. My best guess is when we update to serverless components GA then this shouldn't be an issue, and if it is, then we'd close this anyway and raise it on the components core repo. Let's keep it open here for now 👍

[b6pzeusbc54tvhw5jgpyw8pwz2x6gs]

I am also having the same problem, I created an issue in https://github.com/serverless/components repo.

serverless/components#834

[dphang]

Fixed by this: #1658. The above issue has a PR out for the GA components, but we are still using deprecated @serverless/cli so that one needed to be patched in a similar manner. You should be able to run the patched version by deploying using npx serverless-patched as a temp solution for now. Let me know if there are any issues.

[herrlegno]

Will running the patched version be the final solution? as serverless/components#834 and PR are now closed?

Thank you.