Big +1 to getting this FR done. I need to update the auto stop time of 200 workspaces, and restarting them all sounds terrible.

This makes a ton of sense, I'll see if we can prioritize it next month

If your users are able to customize the Autostop timer on their workspaces, they could use the schedule override-stop command.

You should be able to use coder schedule override-stop my-workspace 72h to keep the workspaces alive over the weekend. However, this command doesn't support truly indefinite Autostop suspension (I believe the max is 132 hours).

Would this remedy your issue?

We still may add some functionality to change Autostop without restarting the workspace down the road.

+1

As it's been a while since this feature was requested I'm going to quickly mention what can be done currently to achieve similar to this goal whilst I work on the design for this 👍.

You can use coder schedule extend <workspace-name> <duration from now> (previously override-stop) to extend the deadline of a running container. There is no upper limit to the <duration from now> argument, meaning you could pass something like 8736h to give the workspace an entire year before it shuts down. Now this isn't the same as disabling autostop but it should be sufficient for your use case for now.

Yes this issue has been addressed. However, making changes to workspace schedule still requires a restart. Not sure how easy it would be to make those changes without a restart.