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.

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

Add some SSH notes #2639

Merged
merged 7 commits into from
Aug 25, 2023
Merged

Add some SSH notes #2639

merged 7 commits into from
Aug 25, 2023

Conversation

vinokurig
Copy link
Contributor

What does this pull request change?

Add some info about starting a workspace from SSH Urls

What issues does this pull request fix or reference?

eclipse-che/che-server#539

Specify the version of the product this pull request applies to

next

Pull Request checklist

The author and the reviewers validate the content of this pull request with the following checklist, in addition to the automated tests.

  • Any procedure:
    • Successfully tested.
  • Any page or link rename:
    • The page contains a redirection for the previous URL.
    • Propagate the URL change in:
  • Builds on Eclipse Che hosted by Red Hat.
  • the Validate language on files added or modified step reports no vale warnings.

@github-actions
Copy link

github-actions bot commented Aug 11, 2023

Click here to review and test in web IDE: Contribute

@github-actions
Copy link

github-actions bot commented Aug 11, 2023

🎊 Navigate the preview: https://64e747a904c0f37b1d94d063--eclipse-che-docs-pr.netlify.app 🎊

[IMPORTANT]
====
//TODO: point to the dashboard SSH procedure when https://github.com/eclipse/che/issues/22111 is done.
* If an SSH URL is used to start a new workspace, the SSH key must be propagated, see link:https://github.com/devfile/devworkspace-operator/blob/main/docs/additional-configuration.adoc#configuring-devworkspaces-to-use-ssh-keys-for-git-operations[Configuring DevWorkspaces to use SSH keys for Git operations].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This point should be stripped or reworked for downstreaming; I don't think we want to point to the upstream github repo for docs in downstream.

Maybe we can adopt the Configuring DevWorkspaces to use SSH keys for Git operations section into Che docs? The file is already in .adoc format, though would need a style pass, etc.

Copy link
Contributor Author

@vinokurig vinokurig Aug 14, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need to have a dedicated page about configuring SSH by a secret. When eclipse-che/che#22111 is done we will point to the user friendly dashboard procedure, so the current procedure will be redundant as a too complicated one. @ibuziuk WDYT?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree we don't need a dedicated page and the link to DWO's doc is sufficient here. My concern is that we need to do some additional work when we downstream these docs later, as I don't think we should be linking to Github there (this is not a necessarily concern for this repo, though).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if I understand it correctly, you'll make this part visible later?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@deerskindoll

if I understand it correctly, you'll make this part visible later?

This is already visible:
screenshot-0 0 0 0_4000-2023 08 23-15_51_13
It should be modified later

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

got it! thanks for the clarification

@vinokurig
Copy link
Contributor Author

@deerskindoll Could you please review the PR?

@deerskindoll
Copy link
Contributor

deerskindoll commented Aug 23, 2023

I created a PR that will fix the issue with building and validating the PR but it needs to be approved before I can merge it: #2643

Copy link
Contributor

@deerskindoll deerskindoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a couple of suggestions, please check them out.

[IMPORTANT]
====
//TODO: point to the dashboard SSH procedure when https://github.com/eclipse/che/issues/22111 is done.
* If an SSH URL is used to start a new workspace, the SSH key must be propagated, see link:https://github.com/devfile/devworkspace-operator/blob/main/docs/additional-configuration.adoc#configuring-devworkspaces-to-use-ssh-keys-for-git-operations[Configuring DevWorkspaces to use SSH keys for Git operations].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if I understand it correctly, you'll make this part visible later?

Copy link
Contributor

@deerskindoll deerskindoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@vinokurig
Copy link
Contributor Author

@deerskindoll Could you please approve the PR for the merge button to be available.

Copy link
Contributor

@deerskindoll deerskindoll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@deerskindoll
Copy link
Contributor

@deerskindoll Could you please approve the PR for the merge button to be available.

sorry, it was a misclick

@vinokurig vinokurig merged commit 9f80df6 into main Aug 25, 2023
6 checks passed
@vinokurig vinokurig deleted the che-22354 branch August 25, 2023 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants