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
{{ message }}
Repository navigation
Add the ability to rename a workspace. Currently workspace must be deleted and a new one built to workaround this. #2188
Users must delete a workspace and build a new one if they decide they want to name a workspace something else. It's something that's expected and a really inconvenient and poor experience if you are not able to do this.
Definition of Done
Users can change the name of a workspace from UI or CLI if they decide they want to name their workspace something else.
I agree in principle. A problem is this means that persistent resource names (e.g the disk) cannot be named based on the workspace name. Perhaps that's an anti-pattern anyways.
Definitely an anti-pattern to link them that way. Naming them that way isn't terrible because we need to name them something, but we shouldn't attach semantics.
Definitely an anti-pattern to link them that way. Naming them that way isn't terrible because we need to name them something, but we shouldn't attach semantics.
In GCP at least, a disk's name is its ID. There is no way to rename a disk, except by light copying it via snapshot.
I think no matter what we're going to have to treat persistent-across-builds resources differently from throw-away-and-start-over resources. If that means different naming conventions, okay; it just goes on the pile of other things we'll need to manage differently.
changed the title [-]Add the ability to rename a workspace. Seems like a shame you have to delete a workspace and rebuild to do that.[/-][+]Add the ability to rename a workspace. Currently workspace must be deleted and a new one built to workaround this.[/+]on Jun 22, 2022
@tjcran I see this was marked for a sprint but what happened to this issue? It's a pretty big PITA to build up a workspace and then have to recreate it since the name is a bit off. Like, I don't want to actually keep my workspace named donkus...
Activity
ketang commentedon Jun 9, 2022
Yep seems like table stakes.
ammario commentedon Jun 9, 2022
I agree in principle. A problem is this means that persistent resource names (e.g the disk) cannot be named based on the workspace name. Perhaps that's an anti-pattern anyways.
ketang commentedon Jun 9, 2022
Definitely an anti-pattern to link them that way. Naming them that way isn't terrible because we need to name them something, but we shouldn't attach semantics.
ammario commentedon Jun 9, 2022
In GCP at least, a disk's name is its ID. There is no way to rename a disk, except by light copying it via snapshot.
ketang commentedon Jun 9, 2022
I think no matter what we're going to have to treat persistent-across-builds resources differently from throw-away-and-start-over resources. If that means different naming conventions, okay; it just goes on the pile of other things we'll need to manage differently.
tjcran commentedon Jun 22, 2022
@misskniss earmarking for next sprint
[-]Add the ability to rename a workspace. Seems like a shame you have to delete a workspace and rebuild to do that.[/-][+]Add the ability to rename a workspace. Currently workspace must be deleted and a new one built to workaround this.[/+]ammario commentedon Jul 13, 2022
@tjcran I see this was marked for a sprint but what happened to this issue? It's a pretty big PITA to build up a workspace and then have to recreate it since the name is a bit off. Like, I don't want to actually keep my workspace named
donkus...tjcran commentedon Jul 22, 2022
Duplicates #3000 closing this one in favor of that one which has more detail