Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 19 July 2017, 10:30 am PDT.
The report for your podling will form a
+1 on removing the route. I would like to see our downstream
components migrate to something different than the giant monolithic
JSON configuration instead of moving to this new endpoint which is
essentially the same format minus some key information. I agree with
what Rob said; it was an incomplet
Hey Rawlin,
I took a look through our splunk logs and it looks like we don't have
anything at Comcast that has hit that endpoint in the last 90 days.
For this reason, I am +1 on removing.
Thanks,
Dave
On Thu, Jul 6, 2017 at 11:27 AM, Robert Butts
wrote:
> This isn't obsolete, so much as a proto
fwiw, 1.8.0 was lengthy because of the transition to Apache Incubator
-- we had a lot of work there. And 2.0.0 was as well because of the
transition to postgres from mysql. 2.1.0 is expected to be
significantly less trouble, and Eric and I have paved the way to
make it so. We'll be availabl
This isn't obsolete, so much as a prototype. It was intended to be "better"
than the CRConfig and replace it for TR. Much the same way
`configs/monitoring.json` is the "next generation" endpoint for Traffic
Monitor (and which is now used in the Golang TM).
That said, as you say, it's incomplete an
Hey all,
I believe I’ve found an obsolete/broken API endpoint [1] that might be a good
candidate for removal. Here is an example request:
GET /api/1.2/cdns/mycdn/configs/routing
This will return a json object that looks like the following:
{
“response”: {
“trafficServers”: […],
