Hi, Based on the Traffic Ops API rewrite/versioning strategy it was decided to promote the current Traffic Ops Golang implementation to TO 2.0 allowing us to leave behind dangerous/deprecated routes(in Perl) in 1.x.
The routes we deprecate will have a deprecation notice added to the response and will be supported until TC 5.0. As part of the Traffic Ops working group last week we put together a list of routes we think should be deprecated and not carried over to 2.0. The list and reasoning why we think it should be deprecated can be seen at https://gist.github.com/mhoppa/bb5341e6a0617aea9282265b840e0735#deprecation-routes. These routes include: * /capabilities/{{name}} * /capabilities (Only POST, GET will be rewritten) * /cdns/{name}/configs/routing * /divisions/name/{{name}} * /federation_resolvers/{{ID}} * /hwinfo/dtdata * /parameters/validate * /regions/{{region}}/phys_locations * /parameters/{{id}}/profiles * /parameters/{{id}}/unassigned_profiles * /divisions/{{division}}/regions * /api_capabilities (Only POST, GET will be rewritten) * /api_capabilities/{{id}} * /servercheck/aadata * /stats_summary/create (Will be rewritten to be supported as a POST on /stats_summary) * /types/trimmed * /deliveryservice_user * /deliveryservice_user/{{DSID}}/{{userID}} * /to_extensions/{{id}}/delete (Will be rewritten to be supported as a DELETE on /to_extensions) * /cachegroup_fallbacks * /cdns/usage/overview * /riak/stats * /traffic_monitor/stats * /cdns/configs * /cachegroup/{{paramID}}/parameter * /cachegroups/{{paramID}}/parameter/available * /deliveryservices/{{id}}/state Thanks, Michael
