Skip to content

workspace "automatic updates" setting #7463

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Tracked by #7468
spikecurtis opened this issue May 9, 2023 · 0 comments · Fixed by #10099
Closed
Tracked by #7468

workspace "automatic updates" setting #7463

spikecurtis opened this issue May 9, 2023 · 0 comments · Fixed by #10099
Assignees

Comments

@spikecurtis
Copy link
Contributor

Adds backend support for an "automatic updates" setting at the workspace scope.

Automatic updates causes workspaces to attempt to automatically update to the latest template version when they are auto-started.

However, this is only possible if the workspace's present template, and the updated template have "compatible" parameters. This means that each parameter of the updated template must either

  1. Have a parameter of the same name and type from the old template
  2. Be mutable and have a default value

Any new parameter in the new template that is immutable or does not have a default value will cause the auto-start to fail. The user must manually upgrade the workspace, providing the new immutable or required parameters.

This issue covers adding the setting to the database, plumbing it to workspace APIs, and modifying the auto-start behavior as described above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants