Of course, we’re just trying “to play the card” that the original behaviour was a bug in the first place. As an admin, If you want to see enabled and disabled plans as a result of the same

Long time reader... first time poster :D I'm really digging and deconstruction a few different buildpacks trying to understand how they really work. supply, compile, detect, etc. Especially the

If you take the conservative approach it would be a breaking change. We have a tool that validates the CF environment after deployment. In our use case, the service exists with plans x, y, z but plan

Hey, friends! Following up on this one more time before we make a decision (currently favouring that this is not a breaking change). We’ll make a decision how to move forward with this issue this

Woohoo! I can't begin to convey how excited I am about this as a former CAPI PM. -Dieu

Hello, The CAPI team has been working on a document to give operators some guidance with regards to knowing when and how to scale their Cloud Controllers (and related jobs in capi-release) based on

Hello, We have cut istio-release 1.2.0. With this release in addition to weighted routing, we now support envoys sidecars configured by Istio Pilot for app to app communication. We also have support

+100 ... big proponent of making v1 manifests obsolete. Cheers, Corey

Great job BOSH team 👏🏻

Hi, all, Quick final reminder that the CAB call for March is this coming Wednesday 20th @ 8a Pacific. We will have regular highlights, QAs, as well as two exciting talks: 1. YTT: The YAML

Friends of BOSH & CF, In the olden days of BOSH, all IaaS configuration was done in individual deployment manifests, a la "v1 manifests". This became tedious and difficult for operators to mange. In

Hello, folks! We’re considering fixing the bug reported here https://github.com/cloudfoundry/cli/issues/967 We understand that this is just one side of the coin: some admins confused about output of

Hello everybody, after a lot of deliberation and many good conversations, we came to the conclusion that we will go ahead and remove the firehose endpoint in six months. So, in the first release

Hi, all, Reminder that the CAB call for February is Wednesday March 20th @ 8a PST (next week). We will have our regular PMCs highlights and hopefully two talks / demos: 1. “YTT: The YAML

[cross-posting lists for visibility] Dear Friends of BOSH, We are about to have our first BOSH PMC meeting! When? Thursday, March 21st, 8AM Pacific Time Afterwards: Every third Thursday

Hi folks, A reminder that the CF Summit Unconference is happening on Monday April 1st (no joke!) at 6PM local time. There'll be a few talks, a lot of open spaces, free beer and food. The Cloud Foundry

We have cut routing-release 0.187.0. Release Highlights golang version bumped to 1.11.5 cf-tcp-router supports truly seamless reloads details Fix url parsing for forwarded url after route-service pass

The default version of Node.js in the Node.js buildpack will change from the latest 6.x version to the latest 10.x version in the first release of the Node.js buildpack after April 11, 2019. Due to

The first release of the Node.js buildpack after April 11, 2019 will no longer include any versions of Node.js 6.x. These Node.js versions are no longer supported upstream [1]. Please migrate your

Dear Cloud Foundry Community, It is that time of Summit again where we seek your help to nominate yourself or your peers for the Community Awards that will be presented at Cloud Foundry Summit in