Hi guys, I've found several references online to a maven plugin for cloudfoundry (including artifacts in Maven Central), but I noticed the source code is no longer available. Between versions

Hi cf-dev, If you've dug around in nats-release, you may have noticed the nats_stream_forwarder[0]. It's a component that subscribes to the top-level NATS channel ">", produces a log line, and

Hi Sergio, Good to hear. If you want to update the service catalog you can run cf update-service-broker. Greets Christian Sergio Rozenszajn <sergio.rozenszajn(a)sap.com> schrieb am Mi., 24. Mai

Hi Christian, The issue is solved now. After adding some logs I realized that the catalog is read by Cloud Controller only once, during service broker registration. After deleting the service-broker

Hi Christian, I've set bindable to false as you suggested and it is still failing. I added some logs in our "handleBinding" method but it is not reached. I guess Cloud Controller is not trying to

Thanks Mike! Definitely a long time coming. I hadn't known about this functionality, it was so long ago. 😀

It was fun digging this thread out of the archives. Thanks for keeping these features in the CC for so long. Now that we're fully transitioned to Diego you can safely remove debug and console

I've seen this done with shell / batch scripts before. The script would be responsible for making sure that the services have been created and the names match up with what is expected in the manfest

I have cloud foundry deployed on azure machines using bosh. For adding another node to the cluster I made changes in the cloud foundry deployment manifest file and redeployed cloud foundry using 'bosh

Hi collleagues, assumed a CF user has an account somewhere on cf.mybestcloudsolution.com where its app is running. The user has also an account on github where the source code of the app is saved. The

Hi, I am new to cloud foundry hence pardon me if my question is missing something obvious. One of my teammate has posted this

Hi Sergio, on first glance this looks, as you seems to be a problem of your catalog definition because the cloud controller only checks the returned JSON and the return messages/status codes of the

Hi, I've created a service broker in Pivotal CF that generates service instances that should be used as route services. According to the documentation

Hi Jeff, cool stuff. Good to here you bring in that aspect into the community. For me that sounds like the nearly same pattern as with bosh, we talked about at OS Summit in Boston. There are some

Hi Jeff, This is indeed exciting. With our large set of on prem software installations running on more “Enterprisy” Linux distros offering a SUSE stemcell opens up a couple of opportunities.

Thanks to all who attended CAB call last week, and for reviewing our proposal. We will continue addressing comments/questions that are added into the proposal

Exciting stuff. In particular, getting an OS vendor involved in the upstream seems like a really good move for the community overall. :) -- Chip Childers CTO, Cloud Foundry

This is amazing to see. Great work everyone in the project teams, both those that created the Diego / Garden approach and those that maintained the DEA architecture over the EOL period. -- Chip

Hello All, The EOL for the Legacy DEA Backend is today, May 22, 2017 You can find the previous notice of this here [1] and here [2]. Documentation on how to migrate to Diego can be found here

I'm not seeing this information included in the CVE announcement. Can you point me to where this is published please? thanks, Alex