Adds route option for requireDefaultIndex

[tylersmalley]

With the addition of routes that need to be available when an index pattern is not defined, it makes sense declare it on the route. Previously we used a regular expression that was set within Kibana. This allows plugins to create routes which do not require an index.

[tylersmalley]

In response to #7481

[Bargs]

IMO it should be opt in. Index patterns are going to be less and less relevant to the app as a whole as we add more plugins.

Either way, the management landing page itself needs to be accessible without a default index pattern otherwise users won't know how to get to security and such.

[tylersmalley]

The landing page no longer requires an index pattern either. Requiring a default index is now opt-in.

[Bargs]

For dashboard, discover, and visualize, do you think we should set requireDefaultIndex: true as a default for all sub-routes, like it's done for the indices route:

uiRoutes
.defaults(/management\/kibana\/indices/, {
  resolve: indexPatternsResolutions,
  requireDefaultIndex: true
});

[Bargs]

Were the html and css changes intentional? Just making sure they weren't committed on accident.

[tylersmalley]

@Bargs, I moved the requireDefaultIndex requirements for dashboard, discover, and visualize to the defaults as suggested.

The CSS and HTML changes were intentional. There were failing tests on the Advanced Settings page which was due to the actions being off screen because the table was not responsive.

[tylersmalley]

I switched to using the linked text because some paths have trailing slashes and it overall made the interface more predictable.

[Bargs]

LGTM

[Bargs]

@tylersmalley can you port this to the new alpha4 branch jbudz just created as well when you merge? https://github.com/elastic/kibana/tree/5.0.0-alpha4

[tylersmalley]

@Bargs, thanks - will backport to the branch.