So, it appears the delivery service SSL key versioning functionality was migrated into the Traffic Portal client. When generating or adding a new cert to a DS, Traffic Portal will take the current version of the cert (or 1 if it's the first cert) and increment the version when POSTing the new cert. Since the version is an updatable field in the API, that is probably the best course of action. Ideally, though, the client shouldn't have to worry about handling versioning at all, because the API should handle that. But the API was not designed that way, so we're stuck with it until we decide to make a breaking API change. One thing that was missing from the API was actually updating the DS `ssl_key_version` column with the current version, and I've added that bit in #2853.
[ Full content available at: https://github.com/apache/trafficcontrol/issues/2855 ] This message was relayed via gitbox.apache.org for [email protected]
