This PR has been opened: https://github.com/apache/trafficcontrol/pull/5993
On Wed, Jun 30, 2021 at 11:04 AM ocket wrote:
>
> That sounds like a good idea
>
> On Wed, Jun 30, 2021, 09:44 Robert O Butts wrote:
>
> > > I hope if it is true that whoever it is sees this.
> >
> > Should we ask u
That sounds like a good idea
On Wed, Jun 30, 2021, 09:44 Robert O Butts wrote:
> > I hope if it is true that whoever it is sees this.
>
> Should we ask us...@trafficcontrol.apache.org just to be sure?
>
>
> On Wed, Jun 30, 2021 at 9:08 AM ocket wrote:
>
> > +1, but I was considering propos
trying to think exactly what assigning a parameter to a cg would do. i'm
guessing it means that all servers/caches in that cg would inherit that
param? but yeah, i'm +1 if not really used...
On Wed, Jun 30, 2021 at 9:08 AM ocket wrote:
> +1, but I was considering proposing this for API v2 w
> I hope if it is true that whoever it is sees this.
Should we ask us...@trafficcontrol.apache.org just to be sure?
On Wed, Jun 30, 2021 at 9:08 AM ocket wrote:
> +1, but I was considering proposing this for API v2 which dropped a fair
> few endpoints itself, and someone told me that ther
+1, but I was considering proposing this for API v2 which dropped a fair
few endpoints itself, and someone told me that there were people out there
using this for something. Maybe that's no longer true, or maybe it wasn't
even actually true at the time, but I hope if it is true that whoever it is
s
Hey folks,
I'd like to propose we deprecate "cachegroup parameters" in the TO API
and remove their routes from TO API v4.
You might be thinking: "what are cachegroup parameters?" Well, if you
didn't already know, you can currently assign parameters to
cachegroups. However, they don't have any sem
