Support reading devfiles from private repos other than GitHub/GitLab/Bitbucket/Azure

[l0rd]

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 a devfile.yaml at the root of it and creates the corresponding DevWorkspace.

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:

• gerrit
• gogs
• gitea
• gitolite
• sourcehut

the devfile.yaml will be ignored the workspace will fail to start.

Describe the solution you'd like

• 🟣 support AzureDevOps OAuth flow
• Support URLs with basic authentication when resolving a devfile #21998
• The workspace should start even if che-server fails to resolve the devfile #21997
• Add info about starting a workspace from raw devfile location che-docs#2566
• Support GIT+SSH URLs when starting workspaces #22025
• Documentation about Git repositories URLs is not complete #22356
• Use default devfile during workspace startup based on 'ssh://' if devfile can not be retrieved by che-server #22488
• Automatically restart from local devfile when devfile failed to be resolved at startup #22491
• As a User, I want to configure SSH keys from the User Dashboard #22111

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 use https://<che-host>/#<devfile-url>?remotes={<git-repo-url>}.

[l0rd]

related Dev Spaces issue https://issues.redhat.com/browse/CRW-3927

[ibuziuk]

@l0rd given that we now support azure and basic OAuth I believe in order to resolve this issue we need to still fix:

• The workspace should start even if che-server fails to resolve the devfile #21997
• update docs with the flow of having token in URL + remote attribute - https://github.com/eclipse-che/che-docs/pull/2566/files#r1122111228

[l0rd]

Resolving the devfile using the user git credentials or SSH key is important too (today we can only do that with the PAT).

But we can focus on those last 2 issues you mentioned, making things more stable and well documented, and use a separate issue for the resolver that uses git credentials or SSH key.

[l0rd]

I have created the last issue #22356 (documentation) for this epic.
Note that devfile resolution in the case of SSH+GIT URLs has been moved to a separate issue (it had lower priority compared to the rest).

[l0rd]

This issue has been fixed