Mar 11, 2024 · Mar 11, 2024 · Mar 11, 2024 · Mar 11, 2024
diff --git a/coderd/apidoc/docs.go b/coderd/apidoc/docs.go
diff --git a/coderd/apidoc/swagger.json b/coderd/apidoc/swagger.json
diff --git a/codersdk/workspaces.go b/codersdk/workspaces.go

 // UpdateWorkspaceAutostartRequest is a request to update a workspace's autostart schedule.
 type UpdateWorkspaceAutostartRequest struct {
 // Schedule is expected to be of the form `CRON_TZ=<IANA Timezone> <min> <hour> * * <dow>`
 // Example: `CRON_TZ=US/Central 30 9 * * 1-5` represents 0930 in the timezone US/Central
 // on weekdays (Mon-Fri). `CRON_TZ` defaults to UTC if not present.
 Schedule *string `json:"schedule"`
 }

diff --git a/docs/api/schemas.md b/docs/api/schemas.md
Original file line number	Diff line number	Diff line change
Expand Up		@@ -253,6 +253,9 @@ func (c *Client) UpdateWorkspace(ctx context.Context, id uuid.UUID, req UpdateWo

		// UpdateWorkspaceAutostartRequest is a request to update a workspace's autostart schedule.
		type UpdateWorkspaceAutostartRequest struct {
		// Schedule is expected to be of the form `CRON_TZ=<IANA Timezone> <min> <hour> * * <dow>`
Copy link Member kylecarbsMar 11, 2024 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. Is there a reason we don't deprecate this field and instead make`CronTimezone` the property on the struct? Copy link MemberAuthor johnstcnMar 11, 2024 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. Could definitely do this! Main reason was to document. Will file a follow-up.
		// Example: `CRON_TZ=US/Central 30 9 * * 1-5` represents 0930 in the timezone US/Central
		// on weekdays (Mon-Fri). `CRON_TZ` defaults to UTC if not present.
		Schedule *string `json:"schedule"`
		}

Expand Down