Support multiple CF instances

[gberche-orange]

Feature Request Info

Problem you are trying to solve

A single cf-mysql-release deployment being used by multiple distinct CF deployments.

Proposed solution/feature

What is the proposed solution and why do you think it is the best approach to the problem above.

Would you want to open an PR for this feature?

Bug Report Info

Currently:

Currently, a single CF endpoint is configured

cf-mysql-release/jobs/cf-mysql-broker/spec

Lines 38 to 40 in 9c077a9

	cf.api_url:
	description: 'URL of the CloudFoundry Cloud Controller'
	example: 'https://api.your-domain.example.com'

and it then used in quota enforcer dashboard for:

• looking up UAA authorization and token endpoint,
• invoking CC API service permission endpoint

https://github.com/cloudfoundry/cf-mysql-broker/blob/499b039875/lib/configuration.rb#L28-L35

https://github.com/cloudfoundry/cf-mysql-broker/blob/c4ca47aeda9d22a70d51db7683d9c39fa51b611d/lib/configuration.rb#L16-L26

https://github.com/cloudfoundry/cf-mysql-broker/blob/c4ca47aeda9d22a70d51db7683d9c39fa51b611d/app/models/service_instance_access_verifier.rb

Expected:

CC client should dynamically be configured using X-Api-Info-Location header send by CC as described in https://docs.cloudfoundry.org/services/supporting-multiple-cf-instances.html

Steps to Reproduce:

Please provide as much detail as possible.

• Register the cf-mysql-release broker an additional CF deployment (called CF2)
• create service instance from CF2
• try to access dashboard: user gets redirected to CF instance configured in cf-mysql-release

Deployment Context:

Please provide relevant details about your deployment. That might include:

• Are you using cf-mysql-release with a service broker?: Yes

Reference:

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/167246961

The labels on this github issue will be updated when the story is started.