Project

General

Profile

Actions

Idea #14467

open

[SDK] Merge Go ArvadosClient and arvados.Client and migrate to arvados.Client

Added by Peter Amstutz almost 6 years ago. Updated 8 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Start date:
Due date:
Story points:
-
Release:
Release relationship:
Auto

Description

We currently have the intolerable situation of two Go SDKs for Arvados, one arvadosclient.ArvadosClient and the other arvados.Client, and the other packages and system services are roughly split in which API they use.

Propose merging the API of ArvadosClient into arvados.Client. As much as possible this should simply be a matter of wholesale copying over and adjusting to use the struct fields of arvados.Client. Then code which currently uses can ArvadosClient can be migrated by replacing ArvadosClient to arvados.Client without having to rewrite any API calls.


Related issues

Related to Arvados - Idea #8964: [SDKs] Design more idiomatic and convenient Go SDKClosedActions
Related to Arvados Epics - Idea #16082: Port client tools to GoNewActions
Related to Arvados - Bug #13144: [SDKs] Wean all components off old arvadosclient and keepclient librariesNewActions
Actions #1

Updated by Peter Amstutz almost 6 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Peter Amstutz almost 6 years ago

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

Updated by Peter Amstutz almost 6 years ago

  • Target version set to To Be Groomed
Actions #4

Updated by Peter Amstutz almost 6 years ago

  • Related to Idea #8964: [SDKs] Design more idiomatic and convenient Go SDK added
Actions #5

Updated by Tom Clegg almost 6 years ago

I don't think this is the right approach.

The point of the new package is to provide a better API, and migrate callers to it, so we can eventually stop supporting the old API. Importing the old API into the new package seems to defeat the purpose.

It might be helpful to have a list of obstacles to that migration: things that are easy/possible with the old package, but hard/impossible with the new package. Then we can fill in the gaps with better thought out APIs in the new package.

Actions #6

Updated by Peter Amstutz over 4 years ago

  • Target version deleted (To Be Groomed)
Actions #7

Updated by Peter Amstutz about 4 years ago

  • Related to Idea #16082: Port client tools to Go added
Actions #8

Updated by Peter Amstutz over 2 years ago

  • Related to Bug #13144: [SDKs] Wean all components off old arvadosclient and keepclient libraries added
Actions #9

Updated by Peter Amstutz over 1 year ago

  • Release set to 60
Actions #10

Updated by Peter Amstutz 8 months ago

  • Target version set to Future
Actions

Also available in: Atom PDF