+1 on deprecating that endpoint. I think we discussed deprecating this endpoint on the mailing list before, but we really need a better way to deprecate endpoints like this.
For example, deprecated endpoints should return a notice in the `alerts` section of the API response with the reason why and what to use instead, in addition to a notice in the changelog and API documentation. The notice in the alerts section of the API response should be standard across all endpoints so that clients have just a single way to check for deprecation and handle it accordingly. - Rawlin On Wed, Jul 17, 2019 at 8:32 AM Fieck, Brennan <[email protected]> wrote: > > Now that the /cachegroups endpoint supports fallbacks, are we good to > officially deprecate the /cachegroup_fallbacks endpoint? It's still in Perl, > so for it to continue to exist in API v2 would mean rewriting functionality > we already have.
