On Mon, Nov 26, 2012 at 11:24 PM, Lundberg, Emory <emory-lundb...@uiowa.edu> wrote: > On Sep 5, 2012, at 11:00 AM, Kevin Falcone wrote: > > I'd suggest looking at what RTIR's IP address parsing routines are doing. > > To revisit this, I was able to get a scrip that would pick up the first > occurrence of an address using a loop, but it would not pick up other > instances of a match. > > In light of that, I suspect having RTIRFindIP.pm pick up those IP addresses > in transactions like RTIR would be less rickety and suck-prone for someone > that isn't me one day having the unfortunate task of following in my shoes, > but I'm not sure how to include that RTIRFindIP.pm's logic in RT. > Is it better to: > > implement RTIR_FindIP.pm's voodoo as a scrip > hook RTIR_FindIP.pm and its dependancies into my RT as a local plugin > some other non-wrong option that I don't know?
Well, RTIR's FindIP scrip is very self contained. I don't mind it transfering into RT::Extension::ExtractIPs with more configuration options. It makes sense considering that code to support IP custom fields migrated from RTIR to RT. If this extension would be generic and configurable enough. RTIR can just switch over the extension one day. > -------- > We're hiring! http://bestpractical.com/jobs -- Best regards, Ruslan. -------- We're hiring! http://bestpractical.com/jobs
