esArchiver doesn't work with multiple saved object indices

[mikecote]

Now that saved objects can exist on multiple indices (more than just .kibana) #35747. I realized esArchiver doesn't support the change yet.

As I'm converting task manager to use saved objects on a different index #39829. I realized when running tests that the esArchiver doesn't touch the .kibana_task_manager. The index is configured for task manager under uiExports.

uiExports: {
  savedObjectSchemas: {
    task: {
      indexPattern: '.kibana_task_manager',
    },
  },
},

[elasticmachine]

Pinging @elastic/kibana-operations

[spalger]

Yeah, we mostly base our checks on whether the index starts with .kibana, to detect saved object indexes, but we also might not be respecting the index setting when we run migrations... Will need to look into this. For the time being you can use the es service to create some objects in the .kibana_task_manager index.

[tylersmalley]

Going to close this issue. We have been working on migrating all archives with saved objects to use kbnArchiver, which uses the import/export under the hood. This work is tracked here #102552