You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Workspace and project logs are written to from multiple sources (Daytona, Providers, etc.). This leads to issues on how to display certain logs because the CLI does not differentiate between, for example, pull progress, push progress, state messages, workspace or project logs, etc.
Describe the solution you'd like
We should look to how Docker (and similar tools) handle progress messages. Docker streams "events" to the CLI and the CLI then decides on how to display the message based on the terminal size. Having log entries as JSON object would also make it easier for us to style and manipulate logs in the most appropriate way based on terminal size (or other properties).
Additional context
This feature will require providers to update their logging strategy as well. Because of this, it's important that our logger library is well structured.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Workspace and project logs are written to from multiple sources (Daytona, Providers, etc.). This leads to issues on how to display certain logs because the CLI does not differentiate between, for example, pull progress, push progress, state messages, workspace or project logs, etc.
Describe the solution you'd like
We should look to how Docker (and similar tools) handle progress messages. Docker streams "events" to the CLI and the CLI then decides on how to display the message based on the terminal size. Having log entries as JSON object would also make it easier for us to style and manipulate logs in the most appropriate way based on terminal size (or other properties).
Additional context
This feature will require providers to update their logging strategy as well. Because of this, it's important that our
logger
library is well structured.The text was updated successfully, but these errors were encountered: