Not all functionality should be blocked on index pattern creation

[epixa]

This is going to be especially important with the upcoming add data features since they will also handle creating index patterns, but it's a problem for x-pack as well. Which means it's probably a use-case we need to solve for applications in general. Users should be able to access the security UI as well as the monitoring application without having first created an index pattern in Kibana. It shouldn't matter whether one is a top level application (i.e. monitoring) or a utility in management (i.e. security).

This originated from @lukasolson in #7135 (comment)

[epixa]

If at all possible, it would be great to get this sorted for alpha4 since it's a pretty severe limitation.

[Bargs]

This is also sort of related to #7496

While the root cause of that issue is probably some sort of unrelated race condition, if users hit it in the wild they'll get stuck in a loop because the management app won't allow them to access the edit index pattern page where they can set an index pattern as default.

[tylersmalley]

I will be work on this tonight when I get back from NodePDX. Currently, without an index pattern you can still access the add data UI. He is where the regex lives: https://github.com/elastic/kibana/blob/master/src/plugins/kibana/public/management/index.js#L23

[tylersmalley]

@epixa @Bargs

What do you two think of this PR? #7516

It adds requireDefaultIndex as an option to the route that defaults to true.

[tylersmalley]

The PR has been merged.