Thank you DK for leading the amazing evolution of BOSH over these last few years! And congrats Marco, looking forward to your leadership on the future evolution! Cheers, Amit

Hi all, Do you have any data on how significant a problem this is? I assume 99% of a team's work happens in cf or cf-inc orgs, and forks are temporary in service of PR'ing to a repo in cf or cf-inc. F

I haven't tried it myself, but I think colocated the ca_certs job from the os-conf-release might work: https://github.com/cloudfoundry/os-conf-release/tree/master/jobs/ca_certs Amit

Great stuff Dr Nic, lovely blog post! wrote:

Thanks Nic, your early feedback on that note was helpful, keep it coming if you have more! wrote:

Hi all, "BOSH Links" is a feature which simplifies how data is shared between BOSH-deployed jobs that need to collaborate with one another (e.g. a web server and its backing database). Like many BOSH

Hi all, In service of the initiative to remove the hard dependency on Consul for Locks & Service Discovery in CF Runtime <https://docs.google.com/document/d/16O5Rk5tOmHc2Qeya7soVHoASAgrH9jYZ0V3fS58dY1

Awesome! Adding Sabeti, who is now PMing RelInt and will leverage this once it's up on bosh.io. Thanks Amit

Hey folks, In the last few months there's been a noticeable growth in activity on Stack Overflow related to Cloud Foundry questions. Folks who are active on the cf-dev and cf-bosh mailing lists may be

Hey Sylvain, I would second James's question. cf-release submodules other releases for historical reasons. We're moving to shipping a manifest that simply composes multiple releases [cf-deployment <ht

Hi Sankeerth, Can you open an issue on https://github.com/cloudfoundry-incubator/consul-release/issues? It's helpful if you can mention what version of cf-release you're using, and if you can include

Hey all, The CF Release Integration team has extracted a nats-release BOSH release out of cf-release so that it can be independently tested and reused within other deployments. * repo: https://github.

Hey all, The CF Infrastructure team has extracted a postgres-release BOSH release out of cf-release so that it can be independently tested and reused within other deployments. * repo: https://github.c

I've hit issues with pre-start scripts as well. My approach has been to raise GitHub issues (e.g. https://github.com/cloudfoundry/uaa-release/issues/28) when I find them, and hopefully this moves ever

Hey folks, As new features are being added, and hardened, in BOSH around making manifests simultaneously simpler and more flexible [0], the Release Integration team in engaged in a track of work to st

I've invited you to fill out the following form: cf-release Release Notes Feedback To fill it out, visit: https://docs.google.com/forms/d/1m8Z0nQ99WVgbaS9eygj9GdCK2SVXyKGGraX_4_GLfFE/viewform?c=0&amp;

Hey folks, There's an old job in cf-release called nats_stream_forwarder that we want to potentially deprecate. It was intended in the past to help with debugging, but isn't currently seeing much acti

Hi folks, Some of you may have noticed we have not cut a cf-release in some time. I just wanted to share an update on the past and current status. We lost about two weeks due to an unfortunate string

Great! Do you want to start a separate thread for those other questions? Should be easier for others to jump into a new thread. Also, if you're amenable to it, would you mind opening up GitHub issues

You probably need to set the property "uaa.require_https" to false in your manifest. Are you doing all this with no SSL termination at all, or do you have a load balancer doing SSL termination? You co