> Not trying to sideswipe, but could we expose that as an endpoint with a > Golang list as well to solve: > https://github.com/apache/trafficcontrol/issues/2872
While I do agree with the request for an API endpoint that tells the client what API versions are supported, I wouldn't want to overcomplicate *this* particular feature with an API endpoint to expose the information that is in the config file. If we implement that kind of "API information" API endpoint, I wouldn't be opposed to including the currently blacklisted routes in its response as a minor goal, but I don't really think it's warranted by this routing blacklist feature alone. You should have a really, really good reason to blacklist a route or bypass a TO-Go route for the Perl, so this should be a (hopefully) relatively rare operation to begin with. I don't think it would be all that useful for API clients to be able to see the list of currently blacklisted APIs. The API client should be written to properly handle 503s whenever they occur, and to the client it shouldn't matter if the 503 is from the database being overloaded at the time or if the route is blacklisted. - Rawlin
