Skip to content

feat(api): add workspace scheduling data to API response #10621

Closed as not planned
@johnstcn

Description

@johnstcn

Ref: #10596 (comment)

Should we include the datapoints "calculated" here in the API response instead (obviously not the formatting, but timestamps, etc). I'm thinking it'd be better if our CLI was "dumber", and it might help other API consumers too.

GET /workspace/uuid
{
  ...,
  "schedule": {
    "starts_next": time,
    "stops_next": time,
	...
  },
  ...
}

Maybe more fields if it makes sense. Basically I'm thinking if we can avoid the need to call cron.Weekly, etc since a client who wants to know this information will need to be able to parse cron tabs (+ any other business logic that may be releavant).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions