Whenever we decide to do breaking API changes that would rev the TO API version to 2.0, we should fix the DS SSL key endpoints to handle the SSL key versioning rather than making the client increment versions manually in the POST request. `version` should become a read-only field that is returned by the API and matches the DS's ssl_key_version column. On new successful requests, the API will increment the DS's ssl_key_version, store the new certs in Riak using the new version number (as well as "latest"), and return the new version on subsequent GETs of the existing certs. For GET requests, passing `version` as a qstring param should still be supported (as it is today) in order to get previous certs. By default, the "latest" version would be returned (as it is today).
[ Full content available at: https://github.com/apache/trafficcontrol/issues/2877 ] This message was relayed via gitbox.apache.org for [email protected]
