You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So what we want to do is, if the template enforces autostop, the user should never be able to stop it. Is that correct?
I would assume the autostop is just a default value since the user could just start the workspace again after the workspace is stopped anyway 🤔 but if you are sure about this is what we want to have I'm ok 👍
So what we want to do is, if the template enforces autostop, the user should never be able to stop it. Is that correct?
Specifically, the user should not be able to extend autostop. While they can still restart their workspace to reset the timer, admins are frustrated with the user's ability to extend the timer for convenience.
The ability to modify the autostop timer is disabled in the workspace settings when the template "enforces" the setting, we should also disable it here.
Fixes#15515
This change effectively reverts the changes introduced by
#13182 (for
#13078).
We also rename the `override-stop` command name to `extend` to match the
API endpoint's name (keeping an alias to allow `override-stop` to be used).
Users can override the default template Autostop in the UI even if it's prevented in the template settings.
Tested with both admin and user roles, though I'm not sure if it can be modified via CLI/API from the user.
Effectively makes the "enforce changes..." option obsolete.
Two options for fixing this:
We can disable [+] and leave [-] enabled, since we don't want to prevent users from reducing cloud spend.
Or we can hide the [-] [+] entirely for simplicity.
The text was updated successfully, but these errors were encountered: