more detail on API version about servicebroker HOT 5 CLOSED

#131 includes more information about API versioning, does it satisfy your requirements?

from servicebroker.

It helps, but AFAICS, there's no defined way for the server to indicate its API version back to the client? It would probably make sense for this to be possible, perhaps either via a /version endpoint or by requiring the server to include the X-Broker-Api-Version header in its responses.

from servicebroker.

The spec says

In this scenario the broker may reject the request with 412 Precondition Failed and provide a message that informs the operator of the required API version.

If this doesn't fit your requirements, you can make a change proposal so that it can be discussed by everyone.

from servicebroker.

Hello @jim-minter
In truth, because all enhancements to the spec are backwards compatible, the version header isn't necessary for disparate versions in platform and broker to be compatible. As long as both support the 2.x version series, they should be compatible with the caveat that new features are optional and require both platform and broker to support them.

With regard to a broker returning the version it supports, consider that many features are optional; a broker might support volume services or route service; it might not support asynchronous provisioning but support other latest features. With this in mind, what would a version indicate to a platform client, and how would you expect the platform to behave as a result?

from servicebroker.

Closing due to inactivity.

from servicebroker.