[GitHub] rawlinp opened a new issue #2877: TO API 2.0: handle SSL key versioning in the DS SSL key APIs rather than the client

[GitBox <gi...@apache.org>]

rawlinp opened a new issue #2877: TO API 2.0: handle SSL key versioning in the DS SSL key APIs rather than the client
URL: https://github.com/apache/trafficcontrol/issues/2877
 
 
   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).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services