Deprecating client API v1

[aarontay]

TL;DR:

• Client API v1 is being deprecated pending the following changes:
  -- Release of API v2 and Snap v1.3
  -- Added Tribe support in API v2

Reasoning

Currently, there is certain business logic that resides in the client API v1 that is not evaluated on the server that results in several defects. Client API v2 ensures that the logic and validation are server side. This way, everything / anything that can be done with snaptel can also be done via a curl as well as providing multiple other benefits.

Impact

Prior to updating to client API v2, project repositories currently depending on Snap API v1, such as Swan and raintank, need to ensure current dependencies maintain use on client API v1 and not to the "latest" version of Snap.

How to update to client API v2

See the API v2 documentation for updating and generating the new client.

If you have any further question or you need help to update to client API v2, do not hesitate to reach out to maintainers directly or via our Slack channel.

[andrzej-k]

Hey @aarontay - For how long do you plan to keep API v1 available to the users? Are there plans (dates) for removing API v1 from the code base?

[woodsaj]

https://github.com/intelsdi-x/snap-client-go just 404's for me. Do you need to make that repo public?

[aarontay]

@woodsaj the snap-client-go repo being made pubic is part of what the deprecations is pending on. @candysmurf is there an estimate date set for the client?