+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

+1, this was suggested few years ago, see https://github.com/cloudfoundry/cc-api-v3-style-guide/issues/46 for related exchanges. I however believe that most of the complexity and associated effort in

Recently I had a use case to use CAPI for exporting some app information, and I struggled a bit here and there to both find a client as well as build one myself for v2. I think what could be really

Hi Neil, Thanks for the feedback. We actually created PRs for both, firehose-exporter[0] and to firehose-to-syslog[1]. We will continue working with the maintainers to get these pulled in.

Johannes, A 6 month deprecation window works for Stratos - that should be fine for us to update. If you can work with the firehose-exporter project to get that updated and off the firehose within the

Hi Greg, I'd like to renew related feedback provided last october on the subject at https://lists.cloudfoundry.org/g/cf-dev/topic/26659245#8303 There are many tooling out there that currently rely on

Hi, guys. I'm facing the same problem. I would've liked to peep into the links you gave, Ben, but they are all dead. Can you please share them again? Thanks -- Sent from:

Hi Abby, Am 04.03.2019 um 07:20 schrieb Abby Chau: Commenting works now. Thanks, - Stefan