Great news, thanks Chip for the update, and thanks to the community's vulnerability management team for their continued work on bionic stemcells vulns. Guillaume.

Thanks Marco for the update and to all contributors for their efforts to reach production readiness for bionic stemcell. I wonder whether the security advisories shared at [1] would in the future simi

+1. Many thanks Shannon for your outstanding product leadership in key elements of the platform: first CF service API, then routing and finally networking. Thanks also for your patience dealing with m

Thanks Benjamin for your interest in this talk and the ideas shared around extended use-cases around CF marketplace! Regarding the CF-as-IAM use-case, your understanding is correct, the idea is to per

Hi, Orange has contributed a component to ease sharing of an open-service-broker marketplace among multiple client platforms. See cab recording at [1], and a longer full slide deck at [2] and actual r

+1 The Open Service Broker api (OSB) is a very powerful standard. The cloud service broker now enables authors to leverage the large ecosystem of terraform providers in order to easily surface associa

Thanks Stephan for this proposal. I'm concerned that adding new roles will further increase complexity and degrade UX. This will likely increase the current feeling of combinatorial explosion when rea

Hi Eric, Thanks for the clarifications! Regards, Guillaume.

Hi Eric, Thanks for sharing the plans for perm project with the community. Can you please remind me where more information can be found related to the "evolution of the identity space" ? I could yet n

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