cloudfoundry / cloudfoundry/cf-java-client

Missing support for MultiServiceRegistration

Ouverte
#1,025 2 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@twoseat y travaille déjà.

Depuis le 16/3/2020.

client enhancement operations triaged
Langage dominant
Java
Étoiles
334
Forks
319
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.