> dealing with API versions is so much of a hassle now that we're writing
new endpoints rather than deal with how hard it could be to add a field to
an existing endpoint.
It's not that much of a hassle. We could put it in existing endpoints. It
just gives us more flexibility this way.
You don't d
+1 seems like a good idea
I hate to bring up something with so much potential for derailing an email
thread, but I just wanna point out that dealing with API versions is so
much of a hassle now that we're writing new endpoints rather than deal with
how hard it could be to add a field to an existin
I love this. +1
On Wed, Oct 9, 2019 at 12:46 PM Robert Butts wrote:
> Hi all! We have a proposal for a new feature for TC: Server Capabilities.
>
> Blueprint is here: https://github.com/apache/trafficcontrol/pull/3972
>
> In a nutshell, the problem we're solving is that it's impossible to only
>
Hi all! We have a proposal for a new feature for TC: Server Capabilities.
Blueprint is here: https://github.com/apache/trafficcontrol/pull/3972
In a nutshell, the problem we're solving is that it's impossible to only
use certain Mids for certain Delivery Services. You can manually assign
whatever
