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
{{ message }}
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.
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?
The text was updated successfully, but these errors were encountered:
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.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?The text was updated successfully, but these errors were encountered: