-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[PVC] Prebuild+PVC, user's account without PVC, open from prebuild, still use PVC #12463
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
Comments
🤔 I'm not agree because it should open without PVC and since there is no prebuild, opening the workspace should fall back to git clone. |
This was intentional choice.
Otherwise, if we were to allow user to open PVC prebuild, but user does not have PVC enabled, now we would need to implement the feature of extracting data from PVC and somehow shoveling it into GCS which then gets uploaded into workspace (complicated), or as you suggested @jenting, fall back to git clone, but then user will not get any benefit from PVC use at all. Effectively that user will not be able to use prebuilds, and will not be able to enroll in PVC, since feature flags enablement is an admin feature. So user experience in that case would not be great in my opinion. |
Make sense, the only left concern is if we enable the prebuilds for gitpod projects, and we haven't enable the users and customers PVC yet. WDYT? |
It would be potentially good to indicate to user that they are using PVC, but at the same time, what they really gonna do with that information? |
Okay, agree on you. |
Bug description
Prebuild+PVC, user's account without PVC, open from prebuild, still use PVC
Steps to reproduce
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
#7901
The text was updated successfully, but these errors were encountered: