As a Korifi API user I want to be able to bind to a managed service instance

[danail-branekov]

GIVEN I have enabled the experimental managed services flag in the helm values
GIVEN I have pushed an app
GIVEN I have created a managed service instance
WHEN I POST /v3/service_credential_bindings with the following request body

{
  "relationships": {
    "app": {
      "data": {
        "guid": "my-app-guid"
      }
    },
    "service_instance": {
      "data": {
        "guid": "my-managed-service-instance-guid"
      }
    }
  },
  "type": "app"
}

THEN I get a 202 Accepted response with a Location header pointing me to a bind job
THEN eventually I see the bind job succeeding
THEN I see a credential binding created with the service broker

Dev notes:

• The implementation must invoke Bind on the broker over OSBAPI
• When requesting Bind from the broker, the implementation should send the accepts_incomplete=true query parameter to enable async provisioning
• When the broker binds the service in a sync manner (the broker responds with 200 OK or 201 Created), the implementation must not check for the binding last operation as the binding has been already created and no operation is running
• When the broker responds with 202 Accepted, then the implementation should poll the binding last operation until the operation completes. Once the operation completes, its status must be reflected in the CFServiceBinding
• The binding response credentials object should be persisted in a secret in the same namespace as the CFServiceBinding.
• Bind OSBAPI docs
• Service binding last operation OSBAPI docs
• Synchronous vs asynchronous operations OSBAPI docs
• Managed services proposal
• Create service binding docs