Unfortunately those properties don't actually do what they say. A story has been added to the CAPI backlog to clean those up, and possibly change

hello!

Hi John, I added a story for the upgrade use case [1]. I believe the use case of needing to move the dashboard_url end point that does not correspond to a service lifecycle event is trickier and is

Hi Guillaume, We are looking for a couple more pieces of feedback. All feedback I've received so far has been positive. There was one report recently from Robert Moss about being able to

Hi, I'm wondering whether the experimental async service broker api is now ready to become official, or whether the CAPI team and PMs are still lacking feedback or have some outstanding issues that

-logLevel=info. Shouldn't theregistryname also be in stager arguments? No, that flag is simply a boolean switch [1]. 2015-08-27T18:43:00.50-0400 [STG/0] ERR builder exited with error: failed to

Thanks for the quick response, guys! Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Open Cloud IBM Software Group, Open Technologies email: chrisfer@... twitter: @christo4ferris blog:

Thank you guys for fixing this issue! I am able to push java apps again. -- View this message in context:

i was just able to use the online version of the buildpack again after the new cert started propagating. thanks to all who helped report and work on this so quickly! we're going to do a post-mortem

Hi all, A new cert has been pushed, and it looks like this issue is resolved. Please let me know if you're still experiencing SSL issues when downloading java-buildpack artifacts. wrote:

Disable ssl verification workaround works. https://github.com/kei-yamazaki/java-buildpack/commit/6b0551ce62f3be3b60e687775554f6f5b126cd0c It can push with -b option. cf push <APP-NAME> -b

Hi all, Just an update: This affects: * users of the "online" a.k.a. "uncached" java-buildpack, * users of the "online/uncached" ruby-buildpack 1.5.0 and later who haved opted-in to JRuby. We're

Ah sorry - I wasn't able to see the image of the error on my phone. I thought it was a different error. aleksey.zalesov(a)altoros.com> wrote:

I've reported this and we're working on it. For what it's worth, this should only affect the Java build pack. I don't believe the other ones are using that URL. If you're seeing the message with

Can you clarify how can I do this? It is not problem of our installation SSL cert that can be skipped with —skip-ssl-validation. Aleksey Zalesov | CloudFoundry Engineer | Altoros Tel: (617)

Are you able to work around the issue by skipping SSL validation?

Yup - I can confirm as well. All buildpacks relying on download.run.pivotal.io are failing now. S. wrote:

Hi all, I encountered the same problem. The same problem has occurred even PWS. Please fix as soon as possible.

Hello! Today we can't push apps to CF due to expired SSL certificate of download.run.pivotal.io <http://cf-dev.70369.x6.nabble.com/file/n1404/Screen_Shot_2015-08-31_at_15.png> Here are CF app

Hi, I recently browsed through your business listing and wanted to highlight some key points for consideration. I am sure it will complement your SEOwork to help attract quality visitors and