Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3351

[RN] Allow to configure git services in Che configuration

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Major Major
    • 3.3.0.GA
    • 3.3.0.GA
    • docs
    • False
    • Hide

      None

      Show
      None
    • False
    • Release Notes
    • Hide
      = Improved UX of Git-provider OAuth configuration

      With this update, administrators can select OAuth application Secrets of their Git providers in the `CheCluster` Custom Resource and the OpenShift web console.
      Show
      = Improved UX of Git-provider OAuth configuration With this update, administrators can select OAuth application Secrets of their Git providers in the `CheCluster` Custom Resource and the OpenShift web console.
    • Enhancement
    • Done

      Synced from Eclipse Che issue

      https://github.com/eclipse/che/issues/21577

      Is your enhancement related to a problem? Please describe

      We want to make it simpler for admin to configure Git services in Che (GitHub, Gitlab, BitBucket): it should not be necessary to look at Eclipse Che documentation.

      This first issue is about the CheCluster CR update. There will be another issue dedicated to some new chectl parameters to configure git services.

      Describe the solution you'd like

      Unable to find source-code formatter for language: diff. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
      spec:
         components
         containerRegistry
      +  gitServices:
      +    github:
      +      - secretName: github-oauth-config
      +    gitlab:
      +      - secretName: gitlab-oauth-config
      +        endpoint: https://gitlab.com
      +    bitbucket:
      +      - secretName: bitbucket-oauth-config
      +        endpoint: https://bitbucket.org
         devEnvironments
         networking
      

      The oAuth App id/secret/private.key etc... should not be directly in the CR (no clear text passwords in the CR). The secret field of an oauthApp is the name of an existing Kubernetes Secret that includes the base64 encoded id and secret. That should be documented clearly in the CRD field to avoid that admins need to read Eclipse Che documentation.

      Release Notes Text

      Configuring Git services OAuth will be more straightforward for administrators as it's possible to reference Git servies secrets from CheCluster CRs. On OpenShift those new configuration will be available from the OpenShift Console UI.

              rhn-ecs-pkovar Petr Kovar (Inactive)
              jiralint.codeready Bot Codeready
              Jana Vrbkova Jana Vrbkova
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: