Skip to content

CLI auto-stop extension #1461

Closed
Closed
@greyscaled

Description

@greyscaled

User Story 👥

As a user with a workspace that has a ttl, I'd like to use the CLI to extend my lease.

Details

There are two types of extension scenarios: reactive and pre-emptive. Underneath the hood,
these are effectively the same and can be re-worded as: "I may extend well before shutdown, or as a CTA
when my lease is almost up (example via notification)".

Reactive Extension in a CLI-only approach

When we notify users that their workspace is shutting down (ie: #1414 ), we might give instructions or a
CTA.

Pre-emptive Extension ina CLI-only approach

We may expose an extension command that looks something like:

coder extend <workspace-name> [time]

If [time] is not supplied, we default to 90 mins. [time] may optionally be specified. We should set
an upper bound on [time]. TBD what that upper bound is, but at least two approaches are:

  1. A hard-set upper bound (example 24 hours)
  2. The difference between NOW and the next scheduled start time

Acceptance Criteria

  • A CLI command that extends a lease

Metadata

Metadata

Assignees

Labels

apiArea: HTTP APIcliArea: CLI

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions