As an admin, I want to be able to see what routes map to what applications/org/space

[drnic]

Perhaps this feature already exists but I'm not sure what command to run.

When there is a routing conflict "already being used" I am unsure how to hunt down what application (in what org/space) has mapped that route.

[drnic]

Perhaps show columns "organization", "space" in the cf routes command?

[CardboardMechanic]

@drnic what if we had something like this that you could use to find information about a specific route?

$ cf route my-app.example.com
host: my-app
domain: example.com
app: my-fun-app
space: development
organization: example-org

How would you expect this to work if you were an admin vs. if you were only an org manager and maybe didn't have visibility in to the offending org/space/app?

Adding the proposed columns would get you there, but you're still scanning all the routes looking for the offending one. Plus, the help at least says that cf routes only lists routes for a space, not org - not sure if that's accurate without looking at the code.

[drnic]

Yeah that would be very helpful.

[CardboardMechanic]

We'll get @jrichard to take a look at getting some priority around this feature

[drnic]

If we can agree on the feature, the you or I can get it done. I've learnt not to do UX changes on cf/bosh without discussion first :)

On Wed, Aug 28, 2013 at 3:09 PM, Will Read notifications@github.com
wrote:

We'll get @jrichard to take a look at getting some priority around this feature

Reply to this email directly or view it on GitHub:
#44 (comment)

[CardboardMechanic]

We'd gladly accept a pull request with the appropriate specs to go with it!

On Wed, Aug 28, 2013 at 3:11 PM, Dr Nic Williams
notifications@github.comwrote:

If we can agree on the feature, the you or I can get it done. I've learnt
not to do UX changes on cf/bosh without discussion first :)

On Wed, Aug 28, 2013 at 3:09 PM, Will Read notifications@github.com
wrote:

We'll get @jrichard to take a look at getting some priority around this

feature

Reply to this email directly or view it on GitHub:
#44 (comment)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/44#issuecomment-23452339
.