Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

Add support for service instance sharing #905

Open
jenspinney opened this issue Apr 10, 2018 · 3 comments
Open

Add support for service instance sharing #905

jenspinney opened this issue Apr 10, 2018 · 3 comments

Comments

@jenspinney
Copy link

A new feature allowing service instances to be shared across orgs and spaces was released in cf-deployment version 1.10.0. This doc explains the very simple step required to enable this feature for your service (adding a shareable field to your service-level metadata in the catalog). Have you thought about enabling this for your service?

@cf-gitbot
Copy link
Collaborator

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/156648412

The labels on this github issue will be updated when the story is started.

@hsiliev
Copy link
Contributor

hsiliev commented Apr 10, 2018

Hey Jen,

We followed the rollout in cf-dev, but so far our users did not filed any requests to have sharing enabled.

As metering service we try to isolate one service instance from the other. Sharing an instance also means taking care for all privacy, retention, etc. properties of the data sent to Abacus. So currently we kind of discourage it across orgs. Spaces however make sense.

We need to reach to community to find if this feature makes sense from end-user perspective.

@lurraca
Copy link

lurraca commented May 14, 2018

@hsiliev Thanks for the reply.

Service instance sharing permissions are based on the users space developer access. This allows you to limit service instance sharing just in spaces in an org.

Let us know if you decide to implement this or if you get any feedback from your community.

(SAPI Team)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants