cloudfoundry / cloudfoundry/cf-java-client
Missing support for MultiServiceRegistration
@twoseat arbeitet bereits daran.
Seit 16.3.2020.
- Vorherrschende Sprache
- Java
- Sterne
- 334
- Forks
- 319
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
-
As a cf-java-client user,
-
in order to interact with service whose name is declared from multiple brokers,
-
I need the methods accepting a serviceName to accept an additional serviceBrokerName:
- org.cloudfoundry.operations.services.DefaultServices#listServiceOfferings
- org.springframework.cloud.appbroker.acceptance.fixtures.cf.CloudFoundryService#createServiceInstance
- org.springframework.cloud.appbroker.acceptance.fixtures.cf.CloudFoundryService#deleteServiceInstance
- org.cloudfoundry.operations.services.DefaultServices#getServiceIdByName
- org.cloudfoundry.operations.services.DefaultServices#getSpaceService
- org.cloudfoundry.operations.serviceadmin.DefaultServiceAdmin#enableServiceAccess
org.cloudfoundry.operations.serviceadmin.DefaultServiceAdmin#disableServiceAccess
-
And I need some response objects to include a service broker field
- ServiceInstanceSummary
The related "Multi-Service Registration" feature was added by SAPI team see related user-facing manual, related epic and support by CF CLI in release v6.43.0 :
CF now allows multiple service brokers to offer services with the same name and or to have the same catalogs. (However, brokers themselves must still be given a unique name.)
Note: Multi-service registration is only supported on CC API version 2.125.0 or greater.
Users can specify which broker to use with a new -b flag, which is available on the following commands:
cf create-service
cf enable-service-access
cf disable-service-access
cf purge-service-offering
cf service - now display broker names
cf marketplace now display broker namesImportant Note: If you have two services with the same name, the commands above will now require the -b flag to disambiguate which service and broker you want to operate on.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.