-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
che factory: should be able to override the name, source.repo, source.branch of the workspace that will be created in the url #13617
Comments
@skabashnyuk Do you have feedback/thoughts on this improvement ? |
Nice new feature. Why it's set only as p2 and set to 7.3.0? |
@skabashnyuk no previous triagers looked at this issue before so I was thinking it was not so important. About severity I used P2 as it's an advanced usecase. @skabashnyuk do you have empty room for |
To me this is very important, for example if you want to share a link to a PR: could provide the default devfile.yaml but override the branch. |
Both code & docs PR merged, happy using. |
Description
At the moment when creating a workpace from a devfile, we can use the factory url
For instance: https://che.openshift.io/f?url=https://github.com/eclipse/che-website will create a workspace from the devfile.yaml located in the repo and the workspace name will be generated from the one in the devfile:
che-website
.If a workspace name already exists, it will suffix it with
_1
,_2
, etc ... these name would become unusable for the user who would have to deal with dozen of workspace with the same name.The goal of the issue is to add a new parameter in the query
name
:https://che.openshift.io/f?url=https://github.com/eclipse/che-website&metadata.name=website-work-on-technology-section
would create a new workspace and name it
website-work-on-technology-section
We could also add parameters like
projects.projectname.source.location
andprojects.projectname.source.branch
to override git location and branchThe text was updated successfully, but these errors were encountered: