Describe the bug
The upcoming SODAR server 1.0 release introduces some small but nonetheless breaking changes to the API (see change-logs).
The current sodar_cli built into cubi-tk can not deal with these changes, primarily because the API return values do not match the models built into sodar_cli. Additioanlly. it also does not support the API versioning that is now being introduced.

Proposed solution

Short-Term:
To build a cubi-tk version that is compatible with SODAR server 1.0, we should:

• build a new (breaking) sodar_cli release thta omits the model checks. This should allow all (or at least most) functionality needed for cubi-tk to be usable.
• Test the new cubi-tk build on Sodar staging which already has the new 1.0 version deployed.

Long-Term
The recently added common sodar_api.py already provides the basis for a new implementation of cubi-tk. This should be improved and expanded, to cover all use-cases needed by cubi-tk, so that the "hack" of sodar_cli is not needed anymore.

Proposed solution
If a new maintainer of sodar_cli can be found, then cubi-tk can rely on an updated sodar_cli instead.