Closed wendorf closed 7 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/140507411
The labels on this github issue will be updated when the story is started.
Suggested formats:
provides:
- name: mysql-proxy
type: mysql
properties:
- port
If properties are not renamed before this work is done:
provides:
- name: mysql-proxy
type: mysql
properties:
- cf_mysql.mysql.port
Hello!
We were reviewing this issue earlier today when we noticed:
https://github.com/cloudfoundry/cf-mysql-release/blob/develop/jobs/proxy/spec#L29
Does this currently meet the requirement?
-- Marco N. && Difan Z.
@menicosia @GarfieldIsAPhilosopher no, the link exposed by the proxy needs to be the same as what is exposed by the mysql job, otherwise the proxy cannot be a substitute for the mysql job - the consumer would need to pull a differently-named link property from the proxy as from the mysql job.
Closing this in favor of following through in #154 .
If I am using the proxy to connect to my database, I cannot use BOSH links and must provide the port information directly in my other jobs' properties. Because the proxy is effectively a database (by virtue of acting as the front of a database) it should provide a link that my other jobs can consume.