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

fix: improve git PAT configuration documentation #2567

Merged
merged 9 commits into from
Apr 4, 2023
Merged

Conversation

svor
Copy link
Contributor

@svor svor commented Mar 3, 2023

What does this pull request change?

Updates Deploying Che with support for Git repositories with self-signed certificates and Using a Git-provider access token articles

These PR provides a few updates related to (taken from the related issue):

  • Retrieving BB user id (for the annotation che.eclipse.org/scm-userid) is not straightforward. That's because using the curl command that is linked in the documentation fails with non-authorized. A link to the authentication for BB API should be added too.

  • I didn't know exactly what URL to use: https://{bb-host}/users/{user-slug}/repos/{repo-name}/ didn't work but https://{bb-host}/scm/~{user-slug}/{repo-name}.git. We should support both BB URL schemas.

  • I initially set che.eclipse.org/scm-userid: 2 because BB user id is an integer. But the secret failed to be parsed because a string is expected. We should document that the scm-userid should be wrapped with "" or ''.

  • I didn't know exactly what URL to use: https://{bb-host}/users/{user-slug}/repos/{repo-name}/ didn't work but https://{bb-host}/scm/~{user-slug}/{repo-name}.git. We should support both BB URL schemas.

  • After successfully setting up the PAT secret, git clone continued to fail because BB was using an untrusted SSL certificate. The article "Deploying Che with support for Git repositories with self-signed certificates" should be referenced as an "additional resource".

  • As some point the configmap is referenced as a secret ("All Secrets that hold certificate files...")

  • It's not clear if certs in binary format are supported or not (they are not supported but this sentence is confusing "Also, they can be encoded as binary data, for example, .cer...")

  • It doesn't mention that the certificate chain is required

  • It doesn't mention that in the githost the protocol (i.e. https) is required

What issues does this pull request fix or reference?

eclipse-che/che#21989
https://issues.redhat.com/browse/RHDEVDOCS-4976

Specify the version of the product this pull request applies to

Che 7.62.0
DS 3.6.0
Merge to main
Cherry-pick to 7.62.x, 7.63.x, 7.64.x

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:
  • Builds on Eclipse Che hosted by Red Hat.
  • the Validate language on files added or modified step reports no vale warnings.

Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
@github-actions
Copy link

github-actions bot commented Mar 3, 2023

🎊 Navigate the preview: https://642d2b809a772270fcbe0093--eclipse-che-docs-pr.netlify.app 🎊

@github-actions
Copy link

github-actions bot commented Mar 3, 2023

Click here to review and test in web IDE: Contribute

@github-actions
Copy link

github-actions bot commented Mar 3, 2023

Click here to review and test in web IDE: Contribute

…or-git-repositories-with-self-signed-certificates.adoc

Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
@max-cx max-cx self-assigned this Mar 3, 2023
@svor svor marked this pull request as ready for review March 6, 2023 09:04
@svor svor requested review from rkratky, max-cx, deerskindoll and a team as code owners March 6, 2023 09:04
@svor svor requested a review from ibuziuk March 6, 2023 09:04
svor added 3 commits March 10, 2023 10:21
Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
svor and others added 2 commits April 4, 2023 13:15
….adoc

Co-authored-by: Max Leonov <mleonov@redhat.com>
….adoc

Co-authored-by: Max Leonov <mleonov@redhat.com>
svor and others added 2 commits April 4, 2023 13:21
….adoc

Co-authored-by: Max Leonov <mleonov@redhat.com>
…port-for-git-repositories-with-self-signed-certificates.adoc
@max-cx max-cx merged commit eb3f882 into main Apr 4, 2023
@max-cx max-cx deleted the sv-pat-che-21989 branch April 4, 2023 13:08
max-cx added a commit that referenced this pull request Apr 4, 2023
* fix: improve git PAT configuration documentation

Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>

* Update :page-aliases: installation-guide:deploying-che-with-support-for-git-repositories-with-self-signed-certificates.adoc

Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>

* feat: extend available schemas for BB repos

Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>

* feat: add a schema to start ws with BB repo url and specific branch

Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>

* Update modules/end-user-guide/pages/using-a-git-provider-access-token.adoc

Co-authored-by: Max Leonov <mleonov@redhat.com>

* Update modules/end-user-guide/pages/using-a-git-provider-access-token.adoc

Co-authored-by: Max Leonov <mleonov@redhat.com>

* Update modules/end-user-guide/pages/using-a-git-provider-access-token.adoc

Co-authored-by: Max Leonov <mleonov@redhat.com>

* suggestion to rephrase callout <2> and NOTE in deploying-che-with-support-for-git-repositories-with-self-signed-certificates.adoc

---------

Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
Co-authored-by: Max Leonov <mleonov@redhat.com>
@max-cx
Copy link
Contributor

max-cx commented Apr 4, 2023

Cherry-picked to 7.62.x.
No need to cherry-pick to 7.63.x and 7.64.x because those branches are not created yet, so the merged changes will get there from main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants