Pull Request for users endpoint

2018-09-18 Thread Moltzau, Matthew
Can someone help me in reviewing this pull request? It is for the users rewrite. https://github.com/apache/trafficcontrol/pull/2834 Not sure of everyone’s availability, so I thought I’d ask here.

Re: Traffic Ops profile import/export format

2018-09-18 Thread Dan Kirkwood
one thought that just came to mind -- both forms are JSON, so TP could easily load in and detect which form it is and produce a "deprecated" warning if the old. -dan On Tue, Sep 18, 2018 at 8:48 AM Rawlin Peters wrote: > Mike, > > The old Traffic Ops UI is deprecated and will be removed in 4.0

Re: Traffic Ops profile import/export format

2018-09-18 Thread Rawlin Peters
Mike, The old Traffic Ops UI is deprecated and will be removed in 4.0, but until that point the profile Import/Export in the TO UI should still continue to work. I think the issue at hand is the Traffic Portal profile import/export functionality. That will be changed to use the standard /api/*/pro

Re: Traffic Ops profile import/export format

2018-09-18 Thread Mike Sandman (misandma)
Sorry, point of clarification - after the proposed change, will the Import/Export buttons on the Traffic Ops UI still continue to work (but using a different format)? Or will the Import/Export functionality be gone from the Traffic Ops UI? Thanks, Mike Sandman On 9/18/18, 9:33 AM, "Dave Neuma

Re: Traffic Ops profile import/export format

2018-09-18 Thread Dave Neuman
I am +1 on removing the old Export/Import in favor of using the API. I don't think we need to add a new endpoint to support importing the old version of the export just because someone somewhere might have an old profile export that is not in Traffic Ops anymore and they need to import it. I don'