Azure/open-service-broker-azure

Is subscriptionId and tenantId configurable during service creation?

Opened this issue · 3 comments

febinrejoe commented

Here's my use case, we have two different Azure subscriptions (one for cloud foundry and another for data services like Azure SQL, Redis etc.) The way Azure Service Broker is currently designed, it is tied to a subscription at install time. This makes it difficult for teams on cf to create data services on the Azure subscription they own. If subscriptionId can be taken as a parameter (in the same way as resource group), it will be convenient for teams to create data services on the Azure subscription they own.

If you have any other recommendation for our use case, please let me know.

zhongyi-zhang commented

Please take a look at the section "Multi-Service Registration" in this CF CLI release note: https://github.com/cloudfoundry/cli/releases/tag/v6.43.0. Using multiple service broker instances, does it solve your problem?

xyloman commented

@zhongyi-zhang could you share how this might work with the tile on Pivotal Cloud Foundry?

zhongyi-zhang commented

@xyloman I believe it is same in PCF if it satisfies

Multi-service registration is only supported on CC API version 2.125.0 or greater.

mentioned in the release note.