Traffic ops currently does not handle versioning very well. I think we do
support 1.1 and 1.2 versions of the API, but I think there are only a few
(maybe asns and deliveryservices) that are actually different.
Versioning is something we look to improve as we move to the golang version
of the API.
On Thu, Oct 12, 2017 at 6:50 AM, Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:
> Does Traffic Ops expose a semantic version number as part of its API?
>
> http://semver.org/
> "Given a version number MAJOR.MINOR.PATCH, increment the:
>
> 1. MAJOR version when you make incompatible API changes,
> 2. MINOR version when you add functionality in a backwards-compatible
> manner, and
> 3. PATCH version when you make backwards-compatible bug fixes.
>
> “
>
> We have some TO clients and would like to improve their backwards
> compatibility. Without this version number, it is not easy to determine
> which fields in the API are supported by any given version.
>
> Thanks,
> Eric
>
>
