Skip to content
This repository has been archived by the owner on Jul 6, 2022. It is now read-only.

Is subscriptionId and tenantId configurable during service creation? #721

Open
febinrejoe opened this issue Aug 9, 2019 · 3 comments
Open

Comments

@febinrejoe
Copy link

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
Copy link
Contributor

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
Copy link

xyloman commented Aug 9, 2019

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

@zhongyi-zhang
Copy link
Contributor

zhongyi-zhang commented Aug 14, 2019

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants