Re: Traffic Ops Extensions in Go

On Mon, Oct 1, 2018 at 2:35 PM Robert Butts wrote: > > >there's the question of the plugin interface versioning. How will we be > versioning the plugin interface with guarantees to not break any plugins > outside of our repo? > > The way Grove handles that, which I also put in this README, is by >

Re: Traffic Ops Extensions in Go

Ok, I added to the PR a README.md with (1) instructions for writing a plugin (2) instructions for finding the examples and information about them, and (3) a glossary with definitions of terms used in the readme: https://github.com/apache/trafficcontrol/pull/2513/commits/a9b927c6b6551696b6049442a26

Re: Traffic Ops Extensions in Go

It looks like the latest commits just added the README. It looks much better; the README really clarifies how it should work. I'm not sure exactly what a "plugin version" should do. It seems reasonably expectable that it will follow the same compatibility as the rest of the project. That is, it on

Re: Traffic Ops Extensions in Go

I think some documentation/definitions would be great here as well. Whats a TO extension vs hook vs data? Are there any examples of how they could be used? —Eric > On Oct 1, 2018, at 1:44 PM, Rawlin Peters wrote: > > Can we get a concise README.md on how to create a custom TO plugin > that

Re: Traffic Ops Extensions in Go

Can we get a concise README.md on how to create a custom TO plugin that also links to the examples you've included in the PR? Also as new hooks are added, I think we'll need documentation for every hook to describe where in the request flow the hooks are called and the data available to each hook.

Re: Traffic Ops Extensions in Go

I like the idea of the "microservice_plugin" because really what you are describing is true "Proxy" functionality. So maybe that's what we are looking for, is a "Proxy" config that allows for remote URL's. -Dew On Mon, Oct 1, 2018 at 11:04 AM Robert Butts wrote: > Yeah, we could write a framew

Re: Traffic Ops Extensions in Go

Yeah, we could write a framework like that. But this framework is strictly more powerful than that. Would you want both? Seems simpler to just have one plugin framework that can do both. In fact, if you wanted, you could add a generic "microservice plugin" as a plugin, which looks at the config fi

Re: Traffic Ops Extensions in Go

Yea, I don’t mean edit the routes.go to add your service and compile it in, but make it so that you can have a dynamic list of Path -> absolute URL So for example /api/1.3/myawesomeextensiton http://myushost.com/mypath Would result in that path calling that absolu

Re: Traffic Ops Extensions in Go

@jan this is for extensions, for code an organization isn't able to open source. Sure, you could just add a line to `routes.go` if you want. You can do that right now. But you'd have to deal with regular merge conflicts. With this dedicated plugin system, the plugins are self-contained, you don't

Re: Traffic Ops Extensions in Go

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 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 plu

Traffic Ops Extensions in Go

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, j

Re: ATC Fall Summit 2018 - Registration and CFP

The summit is in two weeks! We have had several people mention that they are interested in attending that haven't yet registered, so please register if you plan on attending. We also have several speaking spots available still, so please send us an email if you are willing to present. Thanks, Dave