Re: Defining a singular plan for all services
Shannon Coen
Hello Kayode,
toggle quoted messageShow quoted text
So glad to hear you're building a broker for your API Gateway! If your broker offers multiple services, and/or multiple plans of a service, it is up to you as the broker author to expose all of these plans individually in the catalog endpoint [1]. The Service Broker API doesn't support the notion of a "default plan" shared by multiple services because, while plans may have metadata in common, every plan must have a unique identifier. As Cloud Foundry is not prescriptive about implementation or deployment of your broker, mention of settings.yml is a bit confusing. While you may use a configuration file called settings.yml, another service broker author may use a very different mechanism for configuration. [1] http://docs.cloudfoundry.org/services/api.html#catalog-mgmt Warm regards, Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.
On Mon, Oct 19, 2015 at 6:17 AM, Kayode Odeyemi <dreyemi(a)gmail.com> wrote:
A custom built service.
|
|