You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GIVEN I have enabled the experimental managed services flag in the helm values GIVEN I have created a managed service instance WHEN I DELETE /v3/service_instances/service-instance-guid THEN I get a 202 Accepted response with Location header pointing me to the delete operation THEN eventually I see the delete operation succeeds THEN I see the service instance is deleted from the service broker
Dev notes:
The implementation should deprovision the service with the broker over OSBAPI
When requesting service deprovisioning from the broker, the implementation should send the accepts_incomplete=true query parameter to enable async deprovisioning
When the broker deprovisions the service in a sync manner (the broker responds with 200 OK), the implementation must not check for service instance last operation as the instance has been already deprovisioned and no operation is running
When the broker responds with 202 Accepted, then the implementation should poll the service instance last operation until the operation completes.
If the operation succeeds, the CFServiceInstance should be deleted
If the operation fails, the failure should be reflected in the CFServiceInstance status
GIVEN I have enabled the experimental managed services flag in the helm values
GIVEN I have created a managed service instance
WHEN I
DELETE /v3/service_instances/service-instance-guid
THEN I get a
202 Accepted
response withLocation
header pointing me to the delete operationTHEN eventually I see the delete operation succeeds
THEN I see the service instance is deleted from the service broker
Dev notes:
The implementation should deprovision the service with the broker over OSBAPI
When requesting service deprovisioning from the broker, the implementation should send the
accepts_incomplete=true
query parameter to enable async deprovisioningWhen the broker deprovisions the service in a sync manner (the broker responds with
200 OK
), the implementation must not check for service instance last operation as the instance has been already deprovisioned and no operation is runningWhen the broker responds with
202 Accepted
, then the implementation should poll the service instance last operation until the operation completes.If the operation succeeds, the
CFServiceInstance
should be deletedIf the operation fails, the failure should be reflected in the
CFServiceInstance
statusDeprovision service OSBAPI docs
Service instance last operation OSBAPI docs
Synchronous vs asynchronous operations OSBAPI docs
Managed services proposal
Delete service instance docs
The text was updated successfully, but these errors were encountered: