@johnstcn this bit is obnoxious... is it easy to drop?

@ammario This better? #1440

Ideally everything about the workspace is within the existing coder show <workspace>.

In the future, we'll have quotas, autostop, and who knows what, and we don't want a show command for each.

Also we have to talk about your terminal configuration at some point 😉

Oh yeah, I love the next though. It would be cool if in parenthesis it was like "5 days remaining".

Somehow this didn't get auto-merged. It's already done (by #1436)

@vapurrmaid I reopened intentionally to work through an improvement.

@vapurrmaid I reopened intentionally to work through an improvement.

TY for context, all good 👌🏻

@johnstcn where does this sit on your radar?

@johnstcn where does this sit on your radar?

• coder autostart|autostop show is implemented
• coder ls shows schedules

Remaining:

• implement workspace metadata output in coder show (currently only shows resources)

What will the new 'coder show' output look like?

What will the new 'coder show' output look like?

I was thinking of having the metadata in a separate vertical-aligned table, something like the following:

┌───────────────────────────────┐
│ NAME           │ gcp-cian     |
| STATUS         | stopped      |
| AUTOSTART      | 30 9 * * 1-5 |
| AUTOSTOP       | -            |
| // additional fields ...      |
└───────────────────────────────┘
┌──────────────────────────────────────────────┐
│ RESOURCE                  STATUS      ACCESS │
├──────────────────────────────────────────────┤
│ google_compute_disk.root  persistent         │
└──────────────────────────────────────────────┘

However, I'm open to suggestions!

We moved away from pretty tables in coder ls in favor of parsability:

WORKSPACE       TEMPLATE  STATUS   LAST BUILT  OUTDATED  AUTOSTART    AUTOSTOP
ammario/basher  coder     Running  4d23h       false     0 9 * * 1-5  -

I think this is the right call for each of our commands. Perhaps something like:

NAME ammar
AUTOSTART xxx

🤷🏽‍♂️

Closed in favor of #1646