Hi folks, I have a more general question. How do you troubleshoot applications in production? Normally applications in production are scaled with multiple instances and process large number of request

Hi Matt, I would expect the behavior to be the same to the explicit broker update as described in the documentation <https://docs.cloudfoundry.org/services/managing-service-brokers.html#catalog-valida

Hi folks, We need to change the set of plans offered by some of our services dynamically. In our use-case we want to provide a separate plan for each service version. When a new service version is dep

Hi Dan, Thanks for the suggestion. Since our platform is already in productive use and there are also customer applications deployed on it, we cannot afford a breaking change. Also configuring the pro

Hi Stephen, It seems Application Security Groups could address some of our security concerns. Still ASGs have some limitations. We don't want to restrict internet access in platform-wide ASGs as this

Hi Stephen, Thank you again for your thorough explanation. We will explore further those CF features and check if they meet our requirements. Best regards, Peter

Hi Stephen, Thank you for the useful insights. Still I have some further questions and comments. *relevant for production environments where any risk of application I think this is relevant for most e

Hi, For a long time I felt there is something wrong with the buildpack concept. When Lattice <http://lattice.cf/> was announced I thought that CF is moving away from buildpacks. Then it turned out thi

Hi, So far it was safe to assume that a service instance and bound applications are in the same space. If a service instance is shared across args/spaces, this is no longer true. Currently a service b

Hi, Try the binary buildpack or a Docker image. There you have most flexibility. Best regards, Petar Raghuvamsi.Uthpala(a)indegene.com> wrote:

Imagine you have to bind one service instance to 2 apps but app A expects it isnamed my-db and app B expects my-sql. You could use tags, but they have their issues too as discussed earlier in this thr

I am not sure about this: *so the same team responsible for naming the service instance are also responsible for the apps consuming it* I expect an app to be deployed in multiple spaces, orgs and even

Hi, Should we expect some performance change with the switch from offline to online buildpacks? BR, Peter

Hi all, I just published a new node.js package for easy lookup of service bindings in Cloud Foundry. https://github.com/dotchev/cf-services It is a simpler alternative to cfenv. Any feedback is welcom

Hi Zach, I am glad you find this idea useful too. Let me know if you need further input. Happy Easter! Peter

The approach with tags has some issues too: - User-provided services have no tags - Ambiguous. Tags are not unique so it is possible that the same tag appears in multiple service instances bound to th

Mixing build & deploy does not seem to be a good idea. Besides other issues it also violates dev-prod parity principle.

Ok, this might work. Will try it. Thanks for the update. wrote:

Yes, tags at service instance level could work. But if you have created a service instance and later you want to bind it to a new app, can you add the tag expected by that app to the existing service

Hello, Currently CF supports service brokers at two scopes - global or space. https://docs.cloudfoundry.org/services/managing-service-brokers.html#register-broker Is it possible to provide support als