Re: Recommendations for Service parameters

Matt McNeeney

Hey Aniruddha,

From a service broker's perspective, there isn't really a difference
between a service binding and a service key (and so the same schema that is
exposed via *service_binding.create *should be used).

The only difference that a service broker sees is that the *app_guid* field
is only sent to service brokers from CC when running *cf bind-service *(the
field is not set when running *cf create-service-key*).

Let me know if that doesn't make sense,

On Mon, Oct 23, 2017 at 5:57 AM Aniruddha Kulkarni <aquila.25(a)>

Hi Matt,
I have one more follow-up question regarding the "schemas"
object in the service metadata. As mentioned in the link above, we can have
"schemas" specified for Service instance "create/edit" and Service binding
"create". CF also supports specifying parameters when creating Service

My question is whether it makes sense to use the Service binding "schemas"
object during service key creation as well, since logically service key and
service binding are similar?


On Wed, Sep 13, 2017 at 7:14 PM, Aniruddha Kulkarni <aquila.25(a)>

Thank you, this looks like exactly what I was looking for.


On Tue, Sep 12, 2017 at 11:08 AM, Matt McNeeney <mmcneeney(a)>

Hi Aniruddha,

A new feature has just been merged into the Open Service Broker API
specification that allows service brokers to use JSON schemes in their
catalogs to define the configuration parameters they accept for creating a
service instance, updating a service instance and creating a service

If you are new to JSON schema, this excellent guide should help you:

This feature will be supported very soon in Cloud Foundry when the next
version of the spec is released.

Let me know if you have any further questions,

On Tue, 12 Sep 2017 at 06:20, Aniruddha Kulkarni <aquila.25(a)>

CF provides support for specifying service parameters during:

1. Service instance creation (cf cli: -c option)
2. Service instance bind to an application.
3. Service key creation.

The format of these parameters is owned by the individual services.

My question is what is the recommendation regarding how to "publish"
the service parameter's format to the end-developers who will be using a
Service? i.e. how will an end developer know about what parameters are to
be provided?

Is there any guidance w.r.t to using the service/service plan metadata
for providing this information?

-Aniruddha Kulkarni



Join to automatically receive all group messages.