search

Azure / open-service-broker-azure

The Open Service Broker API Server for Azure Services
https://osba.sh
MIT License
248 stars 101 forks source link

What do we do about deprovisioning an instance with existing bindings? #28

Closed arschles closed 6 years ago

arschles commented 6 years ago

From @krancour on August 3, 2017 17:11

The k8s service catalog doesn't let this happen, but that is unlikely to be this broker's only client.

Since the OSB spec doesn't explicitly disallow this, I propose we accept it as a possibility and handle it by cascading the delete (deprovision) to any would-be orphan bindings.

I'm not sure what this, ideally, looks like. Do we queue up a whole bunch of unbinds and require those to complete before we queue up the deprovisioning steps? Or do we do the deprovisioning and when we're done, we say the orhpaned bindings are meaningless and we simply delete them from the broker's own datastore?

I'm going to consider this a post-alpha issue, so I'm not assigning it to any existing milestone.

cc @arschles

arschles commented 6 years ago

From @bingosummer on September 5, 2017 3:31

The Cloud Foundry Cloud Controller doesn't let this happen too.

arschles commented 6 years ago

From @krancour on September 5, 2017 14:57

Since the two clients we care about (for the moment) don't allow this, I think this is something we can circle back on someday for the sake of completeness, but it doesn't seem that it needs to be a priority. I'll leave the issue open, but I'm not assigning it to any milestone at this time.

arschles commented 6 years ago

This has been discussed but never decided upon in the OSB spec group. +1 to going with what the two big OSB enabled platforms do

arschles commented 6 years ago

@krancour can you create an issue for this in https://github.com/openservicebrokerapi/servicebroker/issues?