Bug #15935

GitSSH format

Added by Peter Amstutz 7 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

Our documentation says to do this:

    Services:
      GitSSH:
        ExternalURL: git@git.ClusterID.example.com:

"Make sure to include the trailing colon in Services.GitSSH.ExternalURL."

But "arvados-server config-check" doesn't like it:

transcoding config data: parse git@git.ce8i5.arvadosapi.com:: first path segment in URL cannot contain colon

Removing the trailing ":" is probably fine but the API server needs to add the ":" back in to "clone_urls". (Assumes anything accessing git is using clone_urls or fetch_url which seems reasonable.)

History

#1 Updated by Peter Amstutz 7 months ago

  • Status changed from New to In Progress

#2 Updated by Peter Amstutz 7 months ago

  • Status changed from In Progress to New
  • Description updated (diff)

#3 Updated by Peter Amstutz 7 months ago

  • Description updated (diff)

#4 Updated by Peter Amstutz 7 months ago

  • Description updated (diff)

#5 Updated by Peter Amstutz 7 months ago

  • Target version changed from 2020-01-02 Sprint to 2020-01-15 Sprint

#6 Updated by Peter Amstutz 7 months ago

  • Target version changed from 2020-01-15 Sprint to 2020-01-02 Sprint
  • Status changed from New to Resolved

Solution: GitSSH should have a leading ssh://, the API server already knows what to do with it. Fixed in documentation.

#7 Updated by Peter Amstutz 7 months ago

  • Assigned To set to Peter Amstutz

Also available in: Atom PDF