I vote that by and large we DO rewrite them, with exceptions for routes that just plain don't work, even in Perl. Those are few, though.
If we don't rewrite them, then Perl will last until API 2.0 has been designed, released and then *another full major release cycle*. That's way too long to have two codebases for the same component, IMO, especially since the rewrite is already 50% complete. On Tue, Nov 12, 2019 at 8:43 AM Hoppal, Michael <[email protected]> wrote: > As the Traffic Ops API is being rewritten from Perl to Golang there has > been several routes that have been deprecated and probably more to come. > > In the deprecation efforts I have seen two strategies: > > > * The route IS NOT rewritten from Perl to Golang and a deprecation > notice is added to the alert response in the Perl handler > * The route IS rewritten from Perl to Golang and a deprecation notice > is added to the alert response in the Golang handler > > I think we should have consistency in our approach and wanted to get > people’s thoughts. > > I would vote that we do not rewrite a deprecated route from Perl to Golang. > > Thanks, > > Michael >
