Hi Ketaki, I'm not able to reproduce that issue on latest CF. -Zach

Hello Prasad, This is actually expected behavior. You can find documentation about service access here https://docs.cloudfoundry.org/services/access-control.html. It notes a limitation at the bottom.

I'm happy to announce that the CAPI and Diego teams have completed work for CF v269 that enables all communication between the two systems to use mTLS. This announcement is the beginning of a migratio

Hello Ketaki, This is a known issue. When a plan is disabled it becomes "invisible" to users. However, we don't remove existing service instances because this would break existing apps. Ideally a user

Hi Stefan, Thanks for checking in. We've currently identified the Diego features required to implement this. The Diego team has fleshed out BBS API changes. The next step will be for them to incept an

Hi Stanislav, Support for multiple query params will not be removed and they will also be supported in V3. We'll take a look at improving our documentation around this. -Zach

Hi Jay, Apps will still have access to all the same environment variables in their runtime environement -Zach

congrats!

Hey all, Here's the implementation proposal: https://docs.google.com/document/d/1PjcEx5_w383AKI9WyJHI4gGDkhIS9mhqwUK5nvmOWUc/edit?usp=sharing And here's the tracker epic: https://www.pivotaltracker.co

This is a followup to the concerns raised in an earlier thread titled "Issue with Routing Release v149-151". That thread notes that there is no issue with those routing releases. The underlying 502 er

Hey Peter, I like the use-case that this proposal allows developers to set their expected service name at development time. I think this is a nice explicit contract and is also portable between Founda

Yes, that is supported using the "--health-check-type none" option for cf push that Leandro mentioned. -Zach

Support for Procfiles is currently being added to Cloud Foundry. It is part of the V3 API, which are experimental at the moment, docs here: http://v3-apidocs.cloudfoundry.org/ You can follow progress

Hey CF-Dev We have been working on a proposal to pull basic zero downtime app deployments into the platform. The proposal is linked below. We would love to hear thoughts on whether this would address

Hey Noburou, The multiple app ports were introduced as an experimental feature. I believe we do not intend to continue supporting them in their current incarnation, and to not currently have a concret

Hey all, Currently task creation is disabled by default, and is enabled using a feature flag. This was to allow billing apps time to update and account for tasks consuming resources. We are now going

As of cf-release v232 there will be some required changes to the blobstore configuration in the cf-release manifest. The linked doc should explain what you will need to do depending on the type of blo

Wayne, Can you verify that you are using the latest bosh-lite stemcell 3147? Older stemcells are known to have issues with consul which is what many of the CF components use for service discovery. Lat

As part of the effort to convert from using NFS to WebDAV as the default blobstore in cf-release, we have made that change for bosh-lite. If you deploy a new cf-release to bosh-lite against an existin

Hey Matt, I'm trying to think of other things that would affect only the endpoints that interact with UAA and would be fixed after a CC restart. I'm wondering if it's possible there are a large number