Background: The original intent behind the routes generation was due to URLs being spread throughout multiple JS files in multiple places within those JS files. We never had centralized routes locations.

I have mentioned and in some places not used the Routes service due to factories being centralized authorities on interacting with the Katello API. In some cases, knowing which of the Routes actions to use can be burdensome and hard to determine. My other thinking is that if Bastion ever moved from being so conveniently located as an inline engine, having access to a function that generates routes like that would become either no longer viable or harder. Routes must also be generated by a developer, which has the potential to lag and be out of date. If people still like Routes, then so be it, but the above is my two cents.