There was already an alias feature suggestion which was declined.
Why don't you simply override sonata_admin_dashboard directly in your routing file with the path you want? No need to alias it.

Yes, I have seen that issue (#6088) but that wasn't about overriden methods, that was just about renaming routes.

Why don't you simply override sonata_admin_dashboard directly in your routing file with the path you want?

Can I do that without using the defaults._controller option? I don't like it to use vendor logical controller names in the global routing file.

I still think aliasing is bad. For one thing, you then have 2 routes for the same thing. E.g. admin_dashboard and sonata_admin_dashboard in your above example. And you will have inconsistent paths, as the overridden route by the third party bundle would still be generated with the old path and your new definition would be used in your code when generating urls.

A probably better alternative would be to use the concept of extension. E.g.

sonata_admin_dashboard:
    path: /admin
    extends: true

In this case the route with the same name is not completely redefined, but instead it will reuse a route with the same name that was defined previously and only change the overriden options. It would be fairly easy to implement in the loader. On top of it one could allow defining the route name that one wants to extend (extends: base_route) which would basically add an alias feature. But as said above, not sure if this is a good thing.

@wouterj @fabpot what do you think of this?

@jfsimon I'm 👍

I'm not convinced that the extend mechanism is a good thing either. But if the patch is small enough, and if it does not introduce side effects, that might be something that we can add. Not a top priority tough.

Closing as it will probably bring more confusion than anything else (see #6088.)