1

When we upgraded to v10 beta, we noticed that our old dashboard URLs now break.

E.g.
v9 – http://foo.redash.bar/dashboards/example-name
v10 – http://foo.redash.bar/dashboards/5-example-name where 5 is the dashboard id; interestingly http://foo.redash.bar/dashboards/5 resolves fine which is nice

I always found the human-readable URLs quite nice and the ID-prepending I can live with. But a few suggestions:

  • Such a breaking change should be in the Changelog – admins like myself would like to tell Redash consumers their bookmarks need updating. Luckily our org really only uses half a dozen or so.
  • Ideally, on upgrade, save the old URLs and re-direct them to the new ones.

Thanks again. Redash is a key part of our infrastructure and we couldn’t imagine life without it.

1 Like
2

Your second solution sounds like what was intended when it was changed (see this comment).

1 Like
3

Thank you for the feedback!

Legacy URLs were: /dashboard/:slug, but new ones are /dashboard**s**/:slug, so in your example it should be http://foo.redash.bar/dashboard/example-name and not http://foo.redash.bar/dashboards/example-name.

Can you please try this and confirm?

2 Likes
4

You are absolutely right; the old URLs actually do redirect. http://foo.redash.bar/dashboard/example-name will successfully redirect to http://foo.redash.bar/dashboards/id-example-name. We don’t need people to update their bookmarks. Whew.

All good; just counter-intuitive the first time we saw it, making us think old URLs were all broken!

“Working as designed” now that I understand the design.

2 Likes
5

Thank you for validating.

@jesse should we make this clearer in the release notes for v10?

1 Like
6

Yes, this will be included the release notes for V10 GM.