@vapurrmaid @johnstcn what are both of your thoughts on this one? I agree that it makes sense to remedy this one.

@johnstcn @vapurrmaid @ammario Can e get a solid Definition of Done for this one to avoid potential delays and ambiguity?

How about:

WORKSPACE     : johnstcn/cians-workspace
CREATED       : 2022-06-10T12:14:48 GMT+1
UPDATED       : 2022-06-10T12:14:48 GMT+1
OUTDATED      : false
TEMPLATE      : coder
STATUS        : running (since 022-06-14T08:08:07 GMT+1)
STOP_AT       : 2022-06-10T18:00:00 GMT+1
SCHEDULE_START: 9:30 AM Mon-Fri Europe/Dublin
SCHEDULE_STOP : +12h 

More fields as required, but no indentation -- it should be grep and awk -friendly.

@johnstcn it seems hard to combine the existing resources view with the new schedule information. What do you think about just showing schedule information in coder schedule show?

@ammario Kyle was suggesting just dropping the fancy table altogether, but we can just put the schedule info under the schedule subcommand if that makes things tidier!

Hmm I think putting it under schedule show makes sense at first because showing resources and schedule usefully under coder show will be a challenge.

But without shouting field labels right?

I suppose field labels only need to be shouty when they're a table header.

Fixed by #2402