Evaluate deploying autosleep with “Shared service instance” support enabled #288
Description
Use case: In some cloudfoundry instances, autosleep isn't made available in the marketplace by CF admins, so users need to register autosleep themselves as space-scoped broker. These users would like to be able to share the autosleep service instance to avoid deploying autosleep app multiple times. In other words, users create service instances in one space (even from a space-scoped broker) and share it in other spaces of the same or different orgs.
The auto enrollment feature still provides value for end users, in the sense that
- new spaces/orgs can get automatically enrolled without user action.
- users don't have to deploy autosleep
See document for shared service instance support in cloud foundry here
https://docs.cloudfoundry.org/devguide/services/sharing-instances.html
Some tasks that come to mind:
-
The broker should allow marking the service as “shareable” enabled via a parameter here https://github.com/cloudfoundry-community/autosleep/blob/develop/doc/publish.md#service-broker
-
Need to relook at autowake-up and at making this configurable https://github.com/cloudfoundry-community/autosleep/blob/develop/spring-apps/autosleep-core/src/main/java/org/cloudfoundry/autosleep/ui/servicebroker/configuration/AutosleepCatalogBuilder.java#L73 Brokers with route forwarding enabled are not eligible for sharing service instances
-
Adapt implementation to read shared instances and their spaces/apps and auto-bind. Basically, autosleep currently reads the apps within the space where the instance is created. The code has to be adapted so that autosleep also checks whether an instance is shared in different spaces and read the apps in the shared spaces and bind to them as well.