Thanks Caitlyn for the fix! This is much appreciated. Best regards, Guillaume.

I was also relying on the CFF rss feed, and observed it is now returning an empty stream. Copying the CFF content team and Dan Janhner from CFF security team in case this email thread got unnoticed an

Hi Abby, It seems that the notification URL [1] mentionned into your email isn't accessible to the OSS community. Can you please share its content if its different from the cf-dev@ announcement? Thank

Hi Elisabeth, Thanks for your prompt reply and action to improve things! Regarding github vs pivotal tracker preference: I believe that what matters most is that the content that the CRCF team produce

Hi, It seems that the CFCR project has switched from using the oss backlog [1] to a backlog which is not yet accessible to the community. Can the permissions please be fixed to allow the community to

Hi Mike, You might be interested in zipcar's hashicorp vault bosh config server api impl: Slides Video https://github.com/zipcar/bosh-vault Guillaume.

We had discussions at Orange on how kerberos could help with browser less, password less experience with cf cli. IFAIK this would however indeed imply 1st class kerberos support in both cf cli and uaa

#uaa #kerberos

+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

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

> Ack - will work on that. :) Chip, any progress on making governance and certification documents available to the community onto github ? Thanks in advance, Guillaume.

Hi Zach, Some feedback related to the deprecation of the CC API V2 in favor of V3: there are many tooling out there that currently rely on the CC API V2 (such as UIs, service brokers, provisionning to

Hi Oleksandr and Shannon, I wonder what's the current plan for routing to CFCR workloads from CFAR ? Is there a concensus towards the proposed usage of TCP router [1] with an associated CloudFoundryRo

Maybe a hint similar to what DNS providers gave to to DNS zone records owners in the blog you referenced (see image copied below) could be added to CF CLI cf delete-domain confirmation prompt such as

Hi, Sorry I had missed the notification team page [4] on the CFF page, I'll then follow up with the notification team on their slack. [4] https://www.cloudfoundry.org/projects/ Thanks, Guillaume.

Hi, I'd like to learn the status of the notifications repo [1], which team is working on it and its backlog. There seems to have some commits this year, which reference a pivotal tracker [3][2], but i

Hi Nikolay, Thanks for sharing the MultiApp proposal and contributing this work to the community. It seems MTA shares many objectives with the terraform providers for cloudfoundry [1], credhub [2] and

Thanks Sabha. This proposal also makes sense to me. This would remove the need for brokers to open ASG and be given admin permission. A link to the proposal doc would be useful. +1 for sharing this pr

Hi Matt, We developed at Orange the following broker which matches your description, https://github.com/orange-cloudfoundry/sec-group-broker-filter Feedback is welcome. Regards, Guillaume.

Thanks Stephen. Guillaume.

Thanks Stephen for opensourcing CF Dev through this proposal, seems great! I wonder whether there is a public backlog for the project ? I see some commits such as [1] apparently refer to pivotal track