Do your service brokers leverage the Org and Space fields in the broker API?
The Open Service Broker API working group is exploring removal of "CF-isms"
from the CF broker API to support adoption of the broker API by other
platforms (e.g. Kubernetes). Our hope is that support from other platform
marketplaces will make implementation of the broker API more compelling for
service providers, as it would enable multiple sales channels, growing the
ecosystem of services available to CF operators.
The organization_guid and space_guid fields are sent to brokers with the
create and update operations. Please let me know if you are aware of
service brokers that leverage these fields, and for what purpose.
Product Manager, Cloud Foundry