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

Great ideas, Guillaume. Especially public pipelines displaying smoke test results for each provider and displaying risk of vulnerability (comparison of the providers deployed version of core vs latest

Today we released routing-release v0.141.0 with support for a zero-downtime migration from etcd to mysql or postgresql as the backing store for the routing-api. We changed our data store because the

here is how you can reproduce the issue: 1. CF PUSH APP with just one instance 2. look at the routes for that app in gorouter routes you will see one IP address bind to that route 3. restage your

Thanks Dieu and Chip for explicitly asking feedback on the 2017 certification process, and leaving time for the CF community to provide such feedback. I see seldom comments in the google docs document

An addendum: if you obtain garden-runc-release tarballs from bosh.io, please update to use the "cloudfoundry" location (https://bosh.io/releases/ github.com/cloudfoundry/garden-runc-release) instead

CVE-2016-6658 Incomplete fix for Credential Vulnerability for Custom Buildpacks Severity Medium Vendor Cloud Foundry Foundation Versions Affected - cf-release versions prior to

+ Pivotal PMs/Anchors for visibility

again this is on our CF deployment broker is also ours .. and app is also ours not on PWS wrote:

Thanks for trying John .. I dont think its broker issue .. or can it be .. it may be app issue but broker is presenting right credentials .. but this is intermittent .. I was wondering is there

I can't reproduce this. After restaging, the app no longer has service instance 1's environment variables. Which service broker is this? Could this be a bug in your service broker where it's reusing

team, we are having a unique issue of service credentials still available to application even after unbind and restage of application.. we looked at the app it is not storing creds anywhere .. this

Hi, all, When the Diego team creates its next final version of diego-release, v0.1488.0, it will no longer support or function correctly with garden-linux. In addition to the work already in flight

Hi John, Unfortunately memory usage inside containers is a bit of a painful topic. I've linked to a really great blog by Heroku on this topic below that goes in to more detail but tl;dr there's not a

folks , any insight ?

Hi Nick, Thanks for you reply. able to assign a space to have access to an Isolation Segment where the “private” stack is available. Other spaces, while able to see the “private” stack with

This is super cool! Thanks Brian ___________________________ Brian Roche Senior Director of Software Engineering Dell EMC | Cloud Platform Team mobile 781 727 7337 follow me

+1 - Can't wait. This looks like it will be a nice step forward for build packs! Dan

If they've read the High Availability CloudFoundry.org page <https://docs.cloudfoundry.org/concepts/high-availability.html> before making a decision, then they reasonably could be. If BOSH is not

Hi, Thanks it is working for me know - don't know the exact reason - but I re-deployed CF and then it start working for me for diego. Still do not sure why that was happening - possibility