feat: Add workspace management for admins #1652
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1652 +/- ##
==========================================
+ Coverage 80.65% 81.12% +0.47%
==========================================
Files 185 191 +6
Lines 6095 6215 +120
Branches 679 692 +13
==========================================
+ Hits 4916 5042 +126
+ Misses 1030 1027 -3
+ Partials 149 146 -3 ☔ View full report in Codecov by Sentry. |
MoritzWeber0
force-pushed
the
workspace-mangement
branch
from
7278922
to
ad38ffa
Compare
|
A Storybook preview is available for commit a020a89. |
MoritzWeber0
force-pushed
the
workspace-mangement
branch
3 times, most recently
from
09bbf89
to
dab5133
Compare
MoritzWeber0
force-pushed
the
workspace-mangement
branch
2 times, most recently
from
a2d012b
to
d1da505
Compare
MoritzWeber0
force-pushed
the
workspace-mangement
branch
2 times, most recently
from
0f6681f
to
a14a7ea
Compare
MoritzWeber0
force-pushed
the
workspace-mangement
branch
from
a14a7ea
to
117be93
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Important
The database migration will fail if there are multiple users with the same user name but different casing! Scan your users list to remove duplicated users before updating.
Implements some parts of #998 and workspace related changes proposed in #1645.
Resolves #191.
The pvc_name and size are now stored in our database, which enables us to use a new algorithm for persistent volume names without breaking existing volumes. The new algorithm is independent from the username and uses a random UUID as name instead.
Even though the workspace/user relationship is modeled as many-to-many relationship, each user can only have one workspace. It's intended to add support for more workspaces in the future and the database structure is already set up properly.
The CLI has been updated and shows all persistent volumes created before this update as "Persistent user workspace (legacy)". In addition, the size and annotations are now preserved when performing a backup / restore of a workspace via the CLI. It also fixes an issue that the Pod isn't terminated if the command is aborted with
CTRL + Cwhile "Waiting for Pod".The workspaces are also displayed in the UI with their corresponding size in the user profiles for administrators. Workspaces incl. their content can be deleted. In addition, workspace are now also cleaned up during user deletion.
This PR also makes username changes non-breaking.