Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Resolve Devfiles from private GH/BB/Gitlab repos even if Che OAuth App is not configured #21189

Closed
Tracked by #20583
l0rd opened this issue Feb 20, 2022 · 2 comments
Closed
Tracked by #20583

Resolve Devfiles from private GH/BB/Gitlab repos even if Che OAuth App is not configured #21189

l0rd opened this issue Feb 20, 2022 · 2 comments
Assignees
@vinokurig
Labels
area/che-server kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.

Comments

@l0rd
Copy link
Contributor

l0rd commented Feb 20, 2022 •
edited
Loading

Is your enhancement related to a problem? Please describe

Sometimes the user that deploys Che doesn’t have admin privileges on the GH/BB/Gitlab service: he cannot setup an OAuth application for Che.

In this scenario, if the Devfile is in a private git repositories, a developer is not able to start a workspace. Even if the git credentials of the developer have been setup (a secret exist in its namespace).

⚠️ This is a typical enterprise Che evaluation use case. The person that setup a Che PoC doesn't have admin privileges for the BitBucket production server but needs to validate the factory flow with a Devfile in a git repository.

Describe the solution you'd like

The che-sever devfile resolver should use the user git credential even if the OAuth application is not setup.
@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. area/che-server area/git labels Feb 20, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Feb 20, 2022
@benoitf benoitf added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Feb 20, 2022
@l0rd l0rd mentioned this issue Jun 3, 2022
Closed
11 tasks
@ibuziuk ibuziuk mentioned this issue Jun 3, 2022
Closed
64 tasks
@vinokurig vinokurig mentioned this issue Jun 10, 2022
Merged
9 tasks
@vinokurig vinokurig mentioned this issue Jun 21, 2022
Merged
6 tasks
@ibuziuk ibuziuk mentioned this issue Jun 28, 2022
Closed
68 tasks
@l0rd
Copy link
Contributor Author

l0rd commented Jul 11, 2022

@vinokurig the only thing that is missing to close this issue is documentation right?

@vinokurig
Copy link
Contributor

Yes, Max Leonov promissed to handle the docs PR https://coreos.slack.com/archives/C0324DHHGKY/p1657539895502879

@svor svor mentioned this issue Jul 19, 2022
Closed
51 tasks
@svor svor closed this as completed Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vinokurig vinokurig

Labels
area/che-server kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@benoitf @l0rd @svor @vinokurig @che-bot