Feature request Alternative to workflow:watch, logs, dashboard, or emails

[EHLOVader]

Platform

( x ) MacOS
( ) Linux
( ) WSL2

Installed Via

( x ) Homebrew
( ) Apt Package
( ) Manually

PHP Version

( ) 7.4x
( ) 8.0
( x ) 8.1

Terminus Version

Terminus 3.3.3

Command Executed

terminus workflow:watch

Proposed behavior

Currently the only way to view output of workflows is having had the foresight to start a terminus workflow:watch in a terminal somewhere. If you didn't get there before the workflow started, or wanted to review after, you are just out of luck.

Adding an alternative to this would be a huge improvement. I've found often you don't know you needed to know what happened in your script that ran at code_sync, or deploy until afterwards when it turns out something failed or just didn't work right.

I think the ideal situation would be adding detailed information to the workflow logs in the dashboard... just like the output seen in the build logs in the code log.

This could be similar to Github actions and other CI/CD systems. Listing the triggered events that happened, the scripts that ran as a result, and their output.

Short of having an interface, adding server logs for quicksilver actions would help. Then we could use a plugin like terminus-site-debug to pull the logs and examine what happened.

The only remaining option I could think of was emailing the user. I've considered potential workarounds in scripts but they seem to run in separate instances, an output buffer as the first script and flush and email at the end wouldn't capture scripts run between that.

Thank you for considering this feature

[ander-murane]

Thank you @EHLOVader, we will discuss internally and follow up if the team decides to work on this feature

[namespacebrian]

Thanks for the feedback, @EHLOVader! This is a known feature gap and there are internal tickets/user stories about it, but we have not determined what approach to take in implementing this functionality in terms of systems, lifecycle, maintainability, ownership, UI/UX, and other considerations. Dashboard modernization is a central issue. There is not currently a timeline due to these open questions. What ultimately emerges might or might not closely resemble the experience/functionality you've describe.

I will try to find a place to add this to a list of customer requests/reports about this feature gap.

I'm going to leave this issue open for now, but if/when we come back and close this issue without having delivered the functionality, rest assured that it won't be that we considered your request and decided not to do it, nor will it be an indication of the priority level this is being given. This is a critical feature gap we know we need to address.