feat: tabbed overview of deployment/logs/errors/etc. on deploy #613
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follows #596 (comment).
In combination with #550 we should have something much improved.
UI propsal coming from #613 (comment) 🤓
This will be key controlled and interactive. Then it's just one view at a time and simpler to manage.
We need to bring in the
docker stack ps --no-truncoutput as well, it's super useful. Whhhhy don't we have this still 🤷toolshed/organising#339 toolshed/organising#225
8f25f4fb24/cli/command/stack/swarm/ps.go (L14-L36)Starting to really think we need a sort of "tabbed" view with the likes of #550 coming down the tubes! It's too much vertical scroll if we have an overview, a polling output and then logs? There are sooooo much logs from even the minimal single container deployments. I think we might need to punt this out to the following version of
abrabecause it's looking like it needs a definite design discussion.This would also cover #550 (comment) where we basically enter a
bubbletealoop as soon as we start the deploy overview, meaning we are in full control of the output screen and can detect key presses, switch tab view / fully switch over to the logs and back to the polling progress again - all in parallel.If someone has less ambitious plans, please let me know. Gonna punt this out to "abra next next" 🤸
Let's merge #667 in here too.
Show logs of deployment on `deploy`/`upgrade`/`rollback`to feat: tabbed overview of deployment/logs/errors/etc. on deployI have a prototype for this. Adding a "navigation" menu to the deploy overview:
That allows you tab switch to logs/errors and back to status with the key in the
[...].The errors output will be the
docker service ps --no-trunc/ healthcheck output / etc. It might be nice to separate this and just stream everything vs. detect if something is an error. Then doing[t]asks [h]ealthor something. Feedback welcome!I'll add
*if new output is shown (e.g. [s]tatus*) so there is some "alert" to the end-user of new output.