Hello,
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?

Regards,
--
-Aniruddha Kulkarni

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
binding:
https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#schema-object

If you are new to JSON schema, this excellent guide should help you:
https://spacetelescope.github.io/understanding-json-schema/

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,
Matt

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

Hello,
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?

Regards,
--
-Aniruddha Kulkarni

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

Regards,
Ani

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

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
binding: https://github.com/openservicebrokerapi/
servicebroker/blob/master/spec.md#schema-object

If you are new to JSON schema, this excellent guide should help you:
https://spacetelescope.github.io/understanding-json-schema/

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,
Matt


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

Hello,
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?

Regards,
--
-Aniruddha Kulkarni

--
-Ani