[Issue]: Breaking Wrong Info on restoring system indices

[stefnestor]

Type of issue

Inaccurate

What documentation page is affected

https://www.elastic.co/docs/manage-data/migrate/migrate-internal-indices

What happened?

You're not allowed to restore system indices via index +8.0 you MUST use feature states. This (a) literally directs you wrong path & (b) uses renames pattern which will prevent those from working in destination cluster.

Additional info

• Example (fleet) how system indices are suppose to be restored: .fleet-actions-results data stream cannot be restored via the fleet feature state elasticsearch#89261
• Some feature states should be restored in conjunction with others. For example kibana and security can be restored by themselves but fleet has kibana dependencies and those should be restored together.

[georgewallace]

@stefnestor Thanks again for this other piece of feedback, we will take a look at this

[eedugon]

@stefnestor , thanks a lot for sharing this.

Quick question before preparing a fix:

Some feature states should be restored in conjunction with others. For example kibana and security can be restored by themselves but fleet has kibana dependencies and those should be restored together.

Is there any doc where that is explained? I don't see any explanation in the doc where feature states are introduced, and neither in the restore feature state doc.

If you share more details about that we can also improve those docs highlighting that fact :)

cc: @shainaraskas

[stefnestor]

Cross-posting from internal : https://www.elastic.co/guide/en/elasticsearch/reference/8.17/snapshots-restore-snapshot.html#restore-feature-state