Support reading devfiles from private repos other than GitHub/GitLab/Bitbucket/Azure #21951
Closed
Labels
area/git/dev-environment-config
Issues and PRs related to the automatic setup of git within a cloud development environment
area/git/oauth-services
OAuth support to authenticate developers with their GitHub, GitLab, Bitbucket etc...accounts
kind/epic
A long-lived, PM-driven feature request. Must include a checklist of items that must be completed.
roadmap/3-months
Epics that are planned to complete in the short term (within 3 months)
severity/P1
Has a major impact to usage or development of the system.
Is your enhancement related to a problem? Please describe
When the developer provides a private git repo HTTP URL (i.e.
https://<che-host>/#<git-repo-http-url>
), Eclipse Che looks for adevfile.yaml
at the root of it and creates the correspondingDevWorkspace
.But that works only for GitHub, GitLab or Bitbucket and only if the git service has been previously configured (OAuth App or PAT). For other git services such as:
thethe workspace will fail to start.devfile.yaml
will be ignoredDescribe the solution you'd like
Describe alternatives you've considered
Add OAuth and PAT support for other git services too.
Additional context
That's an issue for public repos too. But in the case of public repos there is a workaround. Instead of using the common workspace URL (
https://<che-host>/#<git-repo-url>
) the developer should usehttps://<che-host>/#<devfile-url>?remotes={<git-repo-url>}
.The text was updated successfully, but these errors were encountered: