Re: Service broker authors: have you ever changed your service or plan names?

Sascha Matzke

We've refrained from renaming and extended the service catalog of affected
brokers with additional "new" entries with new names and UUIDs and actively
phased out the old ones (restricted access etc.).

There are so many delicate mechanisms bound to the names of marketplace
services (triggers in buildpacks, spring cloud magic) that renaming
existing services seemed to risky.

A clearer contract about how to handle service and service plan names would
definitely help (are the names just display names or is it ok to use them



On Tue, Aug 8, 2017 at 11:58 PM, Shannon Coen <scoen(a)> wrote:

The Service Broker API currently supports modifying the service name and
plan name fields, as a uuid is used as the unique identifier. These names
are used in CLI workflows, and are used by applications to parse the
VCAP_SERVICES environment variable to identify credentials. In practice, if
these names are changed it may require updating an application to use the
new service name to identify credentials.

The metadata field is often used to expose display names for services and

The Open Service Broker API working group is interested to know how often
these names actually change, and whether they could be considered immutable
in the future.


Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
Through the darkness of future past
the magician longs to see
One chants out between two worlds
*Fire walk with me*.

Join to automatically receive all group messages.