Maybe as the same we have for bosh release (bosh.io) we can create brokers.cloudfoundry.org wrote:

Hello Kayode, So glad to hear you're building a broker for your API Gateway! If your broker offers multiple services, and/or multiple plans of a service, it is up to you as the broker author to

I think discovery mechanism would be very valuable, especially in cases like this where there was already an S3 service broker open sourced last year:

Awesome! Thank you for the contribution. Would love to see brokers be more easily discoverable. Would someone from the community have the bandwidth to develop a site to make brokered services for CF

Throwing our S3 service broker out there for others that may find it useful -- https://github.com/epoelke/s3-service-broker Currently has default plans for most regions as well as location

Hi, account service implementations could need additional qualifiers to uniquely identify an organization. For example, the implementation I'm working on needs a region along with the guid of the

Hi All, Starting with *CF Release 220*, we have added OpenID Connect ID Token support in UAA. Currently this feature is *disabled* by default to remain fully

Hi Jim, Try setting the `app_domains` property in your manifest to an empty array. Cheers, Amit

Hi, Dieu wrote: > Would be interested to see how this performs on aws or on soft layer. Good point - is there an AWS envrionment we could use? We'll look into Softlayer. > Also, were you able

It works!. Thanks!

sometimes a message like that is due to networking issues. does the bosh director and the VM it is creating have an available network path to reach each other? sometimes ssh'ing in to the VM that is

Thanks Bharath and Amit for the helpful solutions. I have surpassed that error. Now, bosh deploy strucks like in attached image. Could you anyone please? Regards Parthiban A

Hi, this is a possibility. I could find the information using this REST CALL. I have found another

Hello All, We have deployed Cloudfoundry 170 and Configured SSL/TLS. <https://johnpfield.wordpress.com/2014/09/10/configuring-ssltls-for-cloud-foundry/> - Deployment is successful - Able to login -

Good morning Gwenn Can you add more details about your question? WebApp uploads to middleware the file and later it is sent to CF Instance using the

You have an example

Yes, we plan to fully remove support for v1 service brokers at the end of the year.

Have you tried using the nested end point? http://apidocs.cloudfoundry.org/221/apps/list_all_service_bindings_for_the_app.html -Dieu CF CAPI PM bren(a)juanantonio.info> wrote:

Bharath, I think you mean to increase the *disk* size on the compilation VMs, not the memory size. Parthiban, the error message is happening during compiling, saying "No space left on device". This

hi parthiban It seems you are running out of space in your vm in which you are compiling . try to increase the size of memory in your compilation vm . regards Bharath wrote: