Service Broker authors are expected to be cautious when removing services and plans from their catalogs, as Platforms might have provisioned Service Instances of these plans. For example, Platforms might restrict the actions that users can perform on existing Service Instances if the associated service or plan is deleted. Consider your deprecation strategy.
I think, just as bindable can indicate whether an application may bind to instances of a given service/plan, we should, perhaps, add an optional field to service definitions (and overridable in that service's plan definitions, much as with binadable) that could allow a broker to indicate that it can deprovision those services/plans, but will not provision a new one for you.
The spec currently says this:
I think, just as
bindable
can indicate whether an application may bind to instances of a given service/plan, we should, perhaps, add an optional field to service definitions (and overridable in that service's plan definitions, much as withbinadable
) that could allow a broker to indicate that it can deprovision those services/plans, but will not provision a new one for you.