Hi, I would be particularly interested to get feedback on yours and others experience in implementing support for async operations in your service broker and if you have any suggestions for improvemen

Hi Dave, Could you elaborate on your use case for wanting to know the service instance name? It is only unique to the space that the service instance was provisioned in. Dieu CF CAPI PM

Thanks for the reminder Mike. I must have missed that email. Yes, that sounds like a reasonable ask as well. I'll add some stories.

Thanks NIma. I'll have someone on the team take a look. -Dieu CF CAPI PM

Great work!

Thank you for the suggestions Guillaume. We were not planning to enhance this area in the current scope of the v3 work. Could you open up an issue on ccng with your suggestions? I'd like to review wit

On behalf of the CAPI team I'm pleased to announce version 2.6 of the Service Broker API. Two minor changes were introduced in this update. Support for Service Keys was introduced with cf-release v213

At this point the style guide is in draft form. One pair had drafted this to document the patterns that we've fleshed out so far in the v3 cc API. We'll be iterating on it this week as other team memb

So excited for this change! wrote:

Hi all, You can reach those apps for now at their cfapps.io addresses. We're reaching out to the foundation to have them look into why the ip for *.cloudfoundry.org is not redirecting properly. http:/

Hi! Yes, there are plans to change the cf command line to use the v3 cloud controller rest api. You can follow along on progress on stories related to v3 in the CAPI backlog [1] looking at the process

Hi all interested in notifications on modification of resources, It would be helpful for me in framing the "what" and the "why" of this feature if you could also describe your specific use cases and p

On behalf of the CAPI team I'm pleased to announce support for Arbitrary Parameters and Service Instance Tags, two features which extend the possibilities for Cloud Foundry Marketplace service offerin

It is available in cf-release 212. There is a bug being worked on related to session stickiness [1] but if you are not using session stickiness 212 should be fine to use to take advantage of this feat

Hi All, I'm glad to see the interest in this feature. I think this feature is a cross cutting concern across a few teams. I can take this and work on framing the `what` and `why` of the problem and se

There are a few different approaches to this and different concerns that are possible. The requests I've seen have been around wanting to be able to subscribe to and filter the various events that cc

-1 indicates that the state of the instances is unknown. The CLI is purposefully converting the -1 to a ? to indicate that the state is unknown. wrote:

Very cool!

That's odd. I've fixed the link so it should be readable/commentable again. -Dieu CF CAPI PM

This repo is not officially maintained by the cloud foundry foundation. Due to that, it is not as actively updated to stay in synch with the cloud controller api as the cf cli. We do want the api to b