cloudfoundry / cloudfoundry/cf-java-client

Missing support for MultiServiceRegistration

未关闭
#1,025 2 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@twoseat 已经在做这个了。

开始于 2020年3月16日。

client enhancement operations triaged
主要语言
Java
星标
334
派生
319
PR 合并指标
30 天内没有已合并 PR

描述

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

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。