search

openservicebrokerapi / servicebroker

Open Service Broker API Specification
https://openservicebrokerapi.org/
Apache License 2.0
1.19k stars 434 forks source link

Platform notion in case of the catalog endpoint #460

Closed subhankarc closed 6 years ago

subhankarc commented 6 years ago

Hi,

In case of a broker which is consumed from two different envs, there is currently a way to find the consuming env through context in case of provisioning.

But for catalog API, there is no way to know consuming platform. If the broker needs to filter out some plans based on envs, this would be necessary.

In that case, one option could be to register two different path in two different env and identify based on that.

Is there a recommendation to follow in this scenario?

duglin commented 6 years ago

each platform would typically have its own credentials for the broker - so that's another way of knowing.

duglin commented 6 years ago

Closing with the assumption that my response is sufficient

subhankarc commented 6 years ago

Hi @duglin

So basically we should follow either of these two ways.

  1. Register two different path in two different envs and identify based on that.
  2. Identify based on the Users.

Is that understanding correct?

duglin commented 6 years ago

Yes. Either provide each platform with their own URL to the broker, or provide each platform with their own set of credentials (which you should do anyway so that you can revoke them on a per platform basis anyway).