cloudfoundry / cloudfoundry/cf-java-client

Missing support for MultiServiceRegistration

Abierto
#1,025 2 comentarios 0 reacciones 1 asignado Ver en GitHub

@twoseat ya está trabajando en esto.

Desde el 16/3/2020.

client enhancement operations triaged
Lenguaje dominante
Java
Estrellas
334
Forks
319
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

  • 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 names

Important 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.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.