Skip to content

quiet hours: deprecate and eventually remove max_ttl #9284

Closed
@sreya

Description

@sreya

We should only have one scheduling system in the product. We should deprecate and eventually remove the old max TTL-based approach to enforcing workspace shutdown. This should include some sort of warning in the UI and CLI.

  • Add migration that denotes which of max_ttl or autostop_requirement is used for each template
  • Update autostop code to use new table value
  • Update UI to allow one of max_ttl or autostop_requirement (deprecate max_ttl)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions