-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure the management_domain gets registered as a CF route #15
Comments
We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/105876778. |
Was this fixed? |
For some reason Tracker didn't synchronise with Github for this issue... The issue has been closed with the following comment: The multi-tenant broker has been split out of the cf-rabbitmq release and will be soon publicly available again (#59). |
Cool, thanks!
…Sent from my iPhone
On Aug 11, 2017, at 4:43 PM, Diego Lemos ***@***.***> wrote:
For some reason Tracker didn't synchronise with Github for this issue...
The issue has been closed with the following comment:
Issue no longer makes sense as the way route registration is handled has changed over time.
The multi-tenant broker has been split out of the cf-rabbitmq release and will be soon publicly available again (#59).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Currently you can customize the management_domain (used in the Dashboard URL advertised to CF services). However, the route-registrar process on the rabbitmq-broker job does not advertise that domain in a route. Instead it advertises
pivotal-rabbitmq.<system-domain>
. These values should probably be synchronized.The text was updated successfully, but these errors were encountered: