Hello Robert,

Unfortunately, your use use case is not currently supported. dashboard_url
is only supported in the initial response from the broker, even though the
service instance may be asynchronously provisioned. The only workaround I
can think of is to predict the url, though it may not be initially
accessible.

I recognize this as a valid use case, and have asked Dieu (PM for CAPI, now
responsible for the broker API) to consider it for prioritization.

I suggest that we enhance the response to
/v2/service_instances/:guid/last_operation so that when "state":"succeeded"
a header is returned that links to a new endpoint GET
/v2/service_instances/:guid. This endpoint could expose a value for
dashboard_url that wasn't returned in the initial response.

Best,
Shannon



--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Update-Dashboard-URL-with-Asynchronous-Provisioning-tp1313p1377.html
Sent from the CF Dev mailing list archive at Nabble.com.