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


Subhankar Chattopadhyay <subho.atg@...>
 

It would be good to have plan renaming feature, also would be good to
have it only as display name so that it can be changed without much of
dependency. We have also faced similar situations previously.

On Wed, Aug 9, 2017 at 3:40 AM, Mike Youngstrom <youngm(a)gmail.com> wrote:
We have renamed plans and services in the past. I would like to be able to
continue to update them in the future. But I wouldn't consider it a must
have feature but it does has come in handy in the past.

Mike

On Tue, Aug 8, 2017 at 3:58 PM, Shannon Coen <scoen(a)pivotal.io> 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
plans.

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.

Best,

Shannon Coen
Product Manager, Cloud Foundry
Pivotal, Inc.
--




Subhankar Chattopadhyay
Bangalore, India

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.