You're right, tags could work. But, tags didn't exist when we created the convention we have and doesn't seem much of an improvement much over our existing solution. I don't believe our primary client

This is a great idea. Today to get around this issue my org names our service instances with a #value at the end and we use custom VCAP_SERVICES client libraries to ignore anything after the #. That a

Yes, excellent release! We've been anticipating persistent connections from router to instance for a long time. Great work! Mike

Got it, so what I said before hold. We view access control as a must and partitioned routing table a nice to have. Thanks, Mike

Question, Just want to make sure I'm following you. In your Access Control example you mention that without access control a developer would be able to create a route to foo.example.com in a space ass

Thanks Shannon. FWIW we strip the first timestamp from log messages sent to Splunk because Splunk doesn't detect the message as JSON unless the entire event is properly formatted json. Either way, I t

Our Splunk configuration requires the timestamp to be early in the log message. Should be fine as the second item. But, might cause issues any further into the message than that. Mike

I like the direction. This change will be good. Mike

It appears this only applies if you have debug enabled on the cloud controller. Correct? https://github.com/cloudfoundry/cloud_controller_ng/commit/21b9db9d1a58b9154f65404b34bf2e9e4c6260ae wrote:

There was this proposal posted a while back. Not sure on the progress: https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/message/BNDLLURLQ3LDELJWWOJAGVWSZPU647IX/

Thanks Nick, we also use the "Local" provider with our enterprise NFS. Mike wrote:

That plan sounds good to me. I'd only ask that we attempt to lock down how long we are going to keep VCAP_APPLICATION around sooner than later. It will take time for our customers to transition their

Interesting. I assumed that you would be able to create multiple process types with the multiple buildpacks. I understand you can only have one named "web" but I thought that if each buildpack returne

We used them in a bunch of insignificant places and in one significant place. Our significant use case is that we have a billing system that associates internal billing codes with organizations and sp

Great release Shannon! I've been waiting for relational db support before we started using the routing api. Do you consider mysql/postresql support production ready with this release or is it still be

I love it! I can also see how this feature will pair nicely with process types support in v3. Nice proposal! Mike

This change wouldn't effect any of my users. Mike wrote:

Not a problem for us. Though I did have some high hopes for it at one point. :) Mike

Anyone know off hand if CC uses online or offline validation? If configurable what config would we look for to know if it is online or offline? Thanks, Mike

An extension point would be more useful than something that only worked on the gorouters. Another thing that mitigates our need for this feature is that most all of our organization's applications (CF