Florian Müller

@georgi-lozev I agree. The right approach would be to return these states in the response of the fetch endpoint. But there are brokers that cannot provide a fetch endpoint. The...

If a broker hands out different credentials to the platform instances, it can use these to identify the calling platform. There is no need for an additional header.

If this header is only supported by CF, the specification should only go into the profile document.

See PR #570.

See also issue #358.

Why is the path part of the ID? I think the extension ID should be something globally unique to distinguish - let's say - two different backup and restore specifications....

I would expect the extension ID to be globally unique and not having the extension base path in it. For example, if I see the extension `urn:osbext:pivotal.io:mysqlbackups:v1`, I know that...

Service Catalog will support namespace scoped brokers: https://github.com/kubernetes-incubator/service-catalog/pull/1826 The K8S broker proxy should support this at some point.

The K8S namespace scope is quite different from CF scoped brokers.