Skip to content

NP Migration: Dashboard URLs #49060

@flash1293

Description

@flash1293

When moving to NP we plan to split up the current "kibana" app into multiple apps for the various parts (discover, dashboard, visualize, management and so on).

To do this we have to migrate the URLs. Currently dashboard is using the following routes:

  • /app/kibana#/dashboards as listing page
  • /app/kibana#/dashboard as new dashboard page
  • /app/kibana#/dashboard/:id as saved dashboard page

URLs are mapped to their respective apps by the URL prefix which means it should not use both dashboards and dashboard as a first path segment.

We can keep both prefixes for now and just re-initialize the app when switching between listing and actual dashboard, but on the new platform we should clean this app as we have to forward URLs anyway. Suggestion:

  • app/dashboards as listing page
  • app/dashboards/create as new dashboard page
  • app/dashboards/view/:id as saved dashboard page

With this scheme we can safely forward existing URLs to their new counterparts. It is also close to the URLs of visualize ( /visualize for listing, /visualize/create for new visualizations, visualize/edit/:id for existing visualizations). Having /view/:id also containing the edit mode is not super nice (having a separate /edit/:id path would be better) but as this is currently part of the app state it's difficult to migrate, so I don't think the complexity is justified.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions