-
Notifications
You must be signed in to change notification settings - Fork 111
Prompt users when cloning Git repositories using an invalid SSH key #995
Conversation
Signed-off-by: Vitaliy Gulyy <[email protected]>
Signed-off-by: Vitaliy Gulyy <[email protected]>
Signed-off-by: Vitaliy Gulyy <[email protected]>
Signed-off-by: Vitaliy Gulyy <[email protected]>
Signed-off-by: Vitaliy Gulyy <[email protected]>
Signed-off-by: Vitaliy Gulyy <[email protected]>
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
Signed-off-by: Vitaliy Gulyy <[email protected]>
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
Co-authored-by: Eric Williams <[email protected]>
Co-authored-by: Eric Williams <[email protected]>
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
It is not clear that it is to upload a private key to the che workspace. What about
What about |
Signed-off-by: Vitaliy Gulyy <[email protected]>
Probably yes, but as I understand, the command must upload a private key from your local machine and register it in the system(your workspace) with
Renamed, thanks. |
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
Usually, you generate a private key and a public key (key pair). upload the public key to github. But they generally come together in the generation phase.
I would recommend to use the same terminology here https://docs.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent. So what about in all the commands related to view/remove/upload commands, talking about |
BTW what is the difference between |
It seems
|
I know, I am talking about having an action to add the key to GitHub IN the notification, if the url is GitHub, instead of the list of commands. My point is that we already have a predefined SSH key so why not to use it? BTW when we added this predefined key the idea was to help unexperienced users and propose them to add the ssh key in the notification when they clone projects via SSH. |
I think inexperienced user will retry cloning and then click on |
@l0rd since you requested the SSH plugin some time ago, it would be nice to see your opinion. We are discussing here two ways
|
Uploading of private keyfile does not work as expected. In fact, the file is uploaded, but need to investigate what's going when the plugins tries to register it with See the issue eclipse-che/che#19109 where I explained the problem and steps to reproduce. BTW, when I uploaded and registered the file by hand, I was able to clone the repository. So, the flow is working. Just need to fix the bug.
|
@vitaliy-guliy I like the option with the "Add Key to GitHub" cc @sympatheticmoose |
If someone has a git ssh url in the devfile, we expect him to understand these kind of doc: https://docs.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent For those people, giving the list of actions to perform in case of failure is the way to go. We can't neither be too specific to Github and cover all the flows with bitbucket or any others private or public git repos. |
Signed-off-by: Vitaliy Gulyy <[email protected]>
Also, in most of the cases, Github users would get through Ssh could be widely used in private git repos with onprem |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
Signed-off-by: Vitaliy Gulyy <[email protected]>
Signed-off-by: Vitaliy Gulyy <[email protected]>
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
[crw-ci-test] |
[crw-ci-test --rebuild] |
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
Signed-off-by: Vitaliy Gulyy <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #995 +/- ##
=========================================
Coverage ? 57.93%
=========================================
Files ? 45
Lines ? 2028
Branches ? 333
=========================================
Hits ? 1175
Misses ? 843
Partials ? 10 Continue to review full report at Codecov.
|
✅ E2E Happy path tests succeed 🎉 See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
I confirm that the ssh notifications buttons work as expected. |
* Improve the UX when cloning Git projects with SSH uri Signed-off-by: Vitaliy Gulyy <[email protected]>
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Single User on K8S (minikube v1.1.1)
|
What does this PR do?
Allows the workspace plugin to handle events when cloning Git projects by SSH uri
When the devfile contain GIT SSH project, the workspace plugin
Screenshot/screencast of this PR
What issues does this PR fix or reference?
eclipse-che/che#13494
HappyPath tests related on SSH
How to test this PR?
Devfile to test
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.
Happy Path Channel
HAPPY_PATH_CHANNEL=stable