Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
git-credentials-secret not created when cloning a private repository that has no devfile
See original GitHub issueDescribe the bug
The git-credentials-secret secret is not created automatically when:
-
The admin has set up the GitHub Oauth app (see docs)
-
A new user tries to create a devworkspace with a private repository that contains no devfile:
-
Click
Create & Open
The Che-theia editor starts, however, the git-credentials-secret secret is not created in the user’s namespace. Therefore the private repository is not cloned unless the user manually provides their GitHub credentials.
Che version
next (development version)
Steps to reproduce
See above
Expected behavior
The git-credentials-secret secret should be created in the user’s namespace when a devworkspace based on a private repository is created.
Runtime
OpenShift
Screenshots
No response
Installation method
chectl/next
Environment
macOS
Eclipse Che Logs
No response
Additional context
No response
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I haven’t checked in-depth but I think this might be happening because there is an IO exception when trying to read a devfile, before the
git-credentials-secretcan be created: https://github.com/eclipse-che/che-server/blob/d8bed4006aba47feb710612b1e19cfcb355cc611/wsmaster/che-core-api-factory/src/main/java/org/eclipse/che/api/factory/server/scm/AuthorizingFileContentProvider.java#L89-L91I’m not able to reproduce this issue anymore for chectl next: