That’s great, thanks for sharing Jim! Benjamin

Hi Carlos, The release notes for the classical Cloud Foundry Node.js Buildpack are in GitHub : https://github.com/cloudfoundry/nodejs-buildpack/releases These need to be read regularly by a human for

Nice work, congrats guys! Benjamin

Very interesting, thank you for the update Amelia ! Benjamin

Congrats Felix and SAP team, and all other CFF contributors for this great achievement! Benjamin

Hi Guillaume, I’ve just finished watching the video playback of the February Community Advisory Board and I’m impressed how creative you guys have been in terms of re-using existing components for new

Thank you David, that’s good to hear. The deadline is approaching fast and people in the community could be surprised that we have so short time ahead. Others will remember the situation was nearly th

Congratulations Eric for the great work done as Diego project lead! Benjamin

Hi Abby, In the documentation for variable substitution, when it’s said: It’s quite unclear what is meant by “partial values”, and the example doesn’t bring an illustration to this. Indeed, correct me

Hello Carlo, I'm definitely interested by your step that checks if any of the certs are close to the expiration date! If you can share this on a Github somewhere it would be perfect! Cdt,/Benjamin GAN

Super cool to get to know this new “cf-deployment-transition” repo! But about cf-deployment in production, is it still blocked on “Downtime testing” as the README states? Or has there been progress on

The road off Consul looks like it is long but necessary. Consul looks like a spof in CF, when you know how much the platform needs it, and when you read that sometimes plain upgrades break it badly. P

Did you look at the doc on api.cloudfoundry.org about any ordering contract for those API calls?

Tip: You can plan a regular "bosh -n deploy --recreate" on each of your deployments, typically once per week. Run by Concourse, ou by a mere cron in your bosh-lite VM if it's just development. Notice:

The .cf.internal DNS domain is taken over by Consul directly whereas DNS requests for all other domains are forwarded to "recursors", which are the external DNS servers used by your bosh deployment. T

As an update, it looks like I’m running into the Node health flapping <https://github.com/hashicorp/consul/issues/1212> issue that is more frequent with consul 0.5.x servers compared to 0.6.x servers.

Thank you Amit for your answer. I ran again in the “all-consuls-go-crazy” situation today, as quite every day actually. As soon as they start this flapping membership issue, the whole cf+diego deploym

Actually, doing some further tests, I realize a mere 'join' is definitely not enough. Instead, you need to restore the raft/peers.json on each one of the 3 consul server nodes: monit stop consul_agent

Very neat! Thanks a lot Eric.

Hi cf devs, I’m running a CF deployment with redundancy, and I just experienced my consul servers not being able to elect any leader. That’s a VERY frustrating situation that keeps the whole CF deploy