Ah boy, forgot about functional tests, I'll assign back to myself until I fix them.

Code LGTM. Thoughts on:

1. Noted above, indices/create/existing and indices/{{id}} may conflict if id === create. Routing should behave fine but it may be misleading
2. The back button isn't catching indices/create and usually takes me back to discover.
3. This is fine for now because there is only one option, but when more are added it might be useful to have the "Add new" button available on indices/create/existing and any new routes

1. I had the same concern, but I couldn't think of a good alternative that didn't look really weird in the context of the page structure. Would #/settings/indices_create/existing seem ok to you?

2. Back button seems to behave a bit oddly in general in the settings app... I'll see if I can do anything about it though.

3. Would the "Add new" button take you back to the landing page with the wizard options? Or do you mean something else?

Zoomed with Rashid and confirmed the back button is an existing issue throughout the settings app. Created a separate issue for it here #5982.

1. It helps. Thoughts on something like indices/id/{{id}}?
2. 👍
3. Yep, the request mostly stemmed from the back button issue, there's no way to get back to the wizard page without reloading. Consistency too, it is available when an index field list is loaded
   

@jbudz Oooo, how about indices/edit/{{id}} since that page is essentially an index pattern editor?

@Bargs Good call, I like it

@jbudz updated the edit index pattern route and added the Add New button to every page but the landing page itself.

Pending passing jenkins, LGTM.

jenkins, test it