Story #14467
open
[SDK] Merge Go ArvadosClient and arvados.Client and migrate to arvados.Client
0%
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
Updated by Peter Amstutz over 5 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz over 5 years ago
- Description updated (diff)
- Status changed from In Progress to New
Updated by Peter Amstutz over 5 years ago
- Related to Story #8964: [SDKs] Design more idiomatic and convenient Go SDK added
Updated by Tom Clegg over 5 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.
Updated by Peter Amstutz over 4 years ago
- Target version deleted (
To Be Groomed)
Updated by Peter Amstutz over 3 years ago
- Related to Story #16082: Port client tools to Go added
Updated by Peter Amstutz about 2 years ago
- Related to Bug #13144: [SDKs] Wean all components off old arvadosclient and keepclient libraries added
Updated by