I've found that while microservices tend to increase dev productivity by allowing devs to work independently, they also tend lead devs into having independent state across microservices; e.g. each

Hi Folks, Due to lack of popular demand, we plan to move https://github.com/cloudfoundry-incubator/cephfs-bosh-release into the cloudfoundry-attic org, unhook it from our CI pipelines, and cease

Hello all, Following the presentation of the BlockHeads broker at today's CAB call, here comes the proposal for its inclusion as a new CF Extensions project. Proposal:

Thanks Zach for confirmation. Fine - I think the only way to achieve what I want to achieve is to use B-G deployment. Lastly - It will be interesting when rolling update will be supported in cf

The buildpack cache in CF is always per-app and foundation-wide. It can only be erased by deleting the app or dropping all cache artifacts on the platform. The system buildpacks are cached on the

Hey Preetam There's not any work to get 'cf restart-app-instance` to update env vars and there is not a way to clone an app. The current canonical method for updating an app's config, is to perform a

Do you mean with "larger system policies" the usage of online vs. offline buildpacks? Or are there configuration parameters in e.g. the CC or Diego to configure the caching policy? In other words:

FYI... Tomorrow 8AM Pacific or 3PM UTC. Zoom soon. Best, dr.max ibm ☁ silicon valley, ca dr.max ibm ☁ silicon valley, ca

Thanks Dan - It's a reasonable guess! Following link has some explanation about why it has not worked on Diego - (The documentation of cf restart-app-instance should have this

Hi Has CF UAA code been developed in a way that is protected against potential SQL injections? Thanks Enrique

I'd guess that it's because you don't ever want to have an inconsistent state across your app instances. If you were able to use `cf restart-app-instance` and see this change then you'd have one app

Rescheduling the call from this week to next week due to travel in Asia. The team working on the "containerize CFAR control plane" effort would like to demo their efforts during the next call. Public

Hello everyone ! I am observing that the new environment variable set to my application using cf set-env is not getting reflected in the container even after cf restart-app-instance is done. Why is it

The Java Buildpack treats the Buildpack cache as an opaque directory. This means that there are larger system policies about whether it's cached per-cell, per-foundation, etc. but from the

The system buildpacks are cached on the cell and bind mounted read-only into each staging container. Buildpack URLs (to a git repo or a zip file) are downloaded every time staging occurs.

Thanks for the explanation. I have one more question: Is there any caching for the buildpack itself? The CC coding looks like the buildpack is downloaded for each staging operation (either as zip

Great news, thans a lot for the update Matt! Am Mo., 18. Juni 2018 um 12:22 Uhr schrieb Matt McNeeney <mmcneeney@...>: -- Freundliche Grüsse Lukas Lehmann

Hey Lukas, Thanks for checking in! We have had further feedback from users who have been trying out this feature and so far of the feedback has been very positive. Given that, we are likely to look

Hi Matt, Just wanted to check back if there is something we can help to make this feature GA? Did you get any further feedback within the last month? Best regards, Lukas Am Mi., 16. Mai 2018 um 13:15

Hi all, The CF CLI app display feedback survey will close today; if you haven't had a chance to take the short survey, we would appreciate your feedback. Thanks! Best, Abby