Are you looking for feedback on this particular implementation or on the general idea? - Natalie

#cf

You should 100% be using cf-deployment for local development at this point. Release Integration is now working with Pivotal CloudOps to transition Pivotal's production CF instance to cf-deployment. On

cf-deployment will be going GA over the next couple of months, and production transitions between cf-release and cf-deployment will be painful. (My team is working on the first one now.) If you set up

To get into a little more detail about the testing differences: OSS CF is tested extensively. Unit tests, automated acceptance tests, production monitoring, engineer and PM. We're kind of obsessed wit

There's no additional security risk, no. Diego (the container runtime engine) has no concept of spaces, so long running processes that happen to be in the same space from the Cloud Controller's perspe

`cf curl /v2/service_instances/#{service_guid}?purge=true -X DELETE` should delete stuck service records. `cf service --guid #{service_name}` will get you the service guid to use in the above command.

CF Release top-level scripts have been moved. The new location is under the `scripts/` folder. Thanks, CF OSS Release Integration Team