Why wouldn’t we just have the routes.go be able to point to an “outside url” that is the micro service?
Rgds, JvD > On Oct 1, 2018, at 09:39, Robert Butts <[email protected]> wrote: > > So, as we move Traffic Ops from Perl to Go, we need a way to write > extensions in Go, like we have in Perl. > > I wrote a plugin system for Go, modeled after the plugin frameworks in > Grove and Traffic Monitor, PR is here: > > https://github.com/apache/trafficcontrol/pull/2513 > > It's by no means complete, just like with Grove, we'll have to add > additional hooks and data as we find the need. But it works, it has basic > hooks, and includes some sample plugins. > > There was a question about microservices, if someone wants to write > extensions to their Traffic Ops as separate services, instead of built into > the same app. This framework allows that, it's easy to make a plugin that > calls out to another service when an endpoint is requested. > > Does anyone object to this PR? Could I get some +1's/-1's so we can get a > feel for whether people are OK with this PR being merged, and using this > plugin system for Traffic Ops going forward? > > Thanks,
