That sounds like a good idea On Wed, Jun 30, 2021, 09:44 Robert O Butts <r...@apache.org> 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 8888 <ocket8...@gmail.com> wrote: > > > +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 > > sees this. > > > > On Tue, Jun 29, 2021, 21:51 Rawlin Peters <raw...@apache.org> wrote: > > > > > 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 semantic meaning within ATC > > > itself and can only possibly have meaning to external systems and/or > > > internal, proprietary plugins. We were using them for that purpose > > > once, but we have since removed all of our cachegroup parameters. I > > > think it's pretty unlikely that the community at large is using this > > > feature, which is why I'm proposing we deprecate it in order to > > > continue the effort of simplifying the data model and the TO API. > > > > > > Let me know if this feature is critical to anyone; otherwise, I will > > > go ahead and get it removed from TO API v4 (it will still be available > > > in v1-3 until those are removed). > > > > > > - Rawlin > > > > > >
