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

DevSpaces getting-started-samples do not work with SSH URL

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Bug Fix
    • Proposed

      Description of problem:

      When defining custom `getting-started-samples` as per the documentation [1]  and defining  the SSH url for the git repository, containing the devfile, the project-clone fails.

       [1] https://docs.redhat.com/en/documentation/red_hat_openshift_dev_spaces/3.24/html/administration_guide/configuring-devspaces#configuring-getting-started-samples

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      sample.json

{
    "displayName": "Test Sample",
    "description": "Test sample",
    "url": "git@github.com:testuser/testdev.git"
}

       

      Launch the custom sample and the project-clone fails with below error:

      2025/11/27 13:33:35 Cloning project testdev to /projects/project-clone-169899011/testdev
Cloning into '/projects/project-clone-169899011/testdev'...
fatal: unable to access 'https://devspaces.apps.<domain>/dashboard/api/git@github.com:testuser/testdev.git/': The requested URL returned error: 403
2025/11/27 13:33:35 Encountered error while setting up project testdev: failed to clone project: failed to git clone from https://devspaces.apps.<domain>/dashboard/api/git@github.com:testuser/testdev.git: exit status 128

       

      Actual results:

      Expected results:

      Reproducibility (Always/Intermittent/Only Once):

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       

       *

              oorel Oleksii Orel
              rhn-support-jyarora Jyotsana Arora
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: