Follow-up to #825 (pause/resume capability for private instances).
Once an instance can be paused, it should also be excluded from default listings (e.g. my_instances and any console/API listing that shows 'active' instances) while paused - so a paused instance doesn't clutter the normal working view. It should still fully exist: config, history, and subscription untouched, and it must reappear in the default listing automatically as soon as it's resumed.
This is a listing/visibility filter, not a deletion or archive-with-data-loss. Likely needs a way to explicitly request paused instances too (e.g. an include_paused flag), for cases where someone does want to see them.
Depends on #825 landing first.
Follow-up to #825 (pause/resume capability for private instances).
Once an instance can be paused, it should also be excluded from default listings (e.g. my_instances and any console/API listing that shows 'active' instances) while paused - so a paused instance doesn't clutter the normal working view. It should still fully exist: config, history, and subscription untouched, and it must reappear in the default listing automatically as soon as it's resumed.
This is a listing/visibility filter, not a deletion or archive-with-data-loss. Likely needs a way to explicitly request paused instances too (e.g. an include_paused flag), for cases where someone does want to see them.
Depends on #825 landing first.