Rawlin Peters

So, exponential backoff retrying is certainly better than non-exponential, but it's really important for there to be jitter in the sleep intervals as well. Otherwise, clients will all retry at...

> t3c runs should already be dispersed. The ATC cache-config itself doesn't do that, users need to make their script do that, but I think the Ansible in the repo...

I agree we need to improve the "select a tenant" dropdown list, but I don't think this flattened layout would be best. The user would still have to bounce around...

Related: https://github.com/apache/trafficcontrol/issues/3258

Yeah, hence the minor label. The DS obviously wouldn't work, but it was kind of confusing when I realized I used the wrong `cdnId` in my request and ended up...

I don't necessarily agree with this note in the docs: > In the vast majority of cases, it is advisable that the PUT method of the [servers/{{ID}}](https://traffic-control-cdn.readthedocs.io/en/latest/api/v3/servers_id.html#to-api-v3-servers-id) endpoint be used...

FYI for whoever picks this up, I think [this](https://github.com/apache/trafficcontrol/blob/a67914f9e4095b8a762ec4914fceee12d542306c/traffic_ops/traffic_ops_golang/server/servers.go#L752-L760) might be the only prepared query we have so far. At least, that's the only one I noticed experiencing an error...

Rather than just controlling the API version, we should have the parameter control the entire URL. That is how most of the TR watchers work today.

 There is a little filter indicator, but I agree it should probably be more prominent at least and easier to clear without...

Personally, I really like the method that TR uses, which is similar to what this "Generic Traffic Ops Config Endpoint" would be. With few exceptions, TR gets all of its...