Remove asciidocs - TODO need to figure some bits of this out

Author: PeteGillinElastic

docs/reference/indices.asciidoc

@@ -24,7 +24,6 @@ index settings, aliases, mappings, and index templates.
 * <<indices-split-index>>
 * <<indices-clone-index>>
 * <<indices-rollover-index>>
-* <<unfreeze-index-api>>
 * <<indices-resolve-index-api>>
 * <<indices-resolve-cluster-api>>
 * <<indices-downsample-data-stream>>
@@ -143,6 +142,5 @@ include::indices/shrink-index.asciidoc[]
 include::indices/simulate-index.asciidoc[]
 include::indices/simulate-template.asciidoc[]
 include::indices/split-index.asciidoc[]
-include::indices/apis/unfreeze.asciidoc[]
 include::indices/update-settings.asciidoc[]
 include::indices/put-mapping.asciidoc[]

docs/reference/indices/apis/unfreeze.asciidoc

@@ -45,6 +45,8 @@ For more information on managing indices, refer to <<indices, Index APIs>>.
 Badges indicate if an index is a <<ccr-put-follow,follower index>>, a
 <<rollup-get-rollup-index-caps,rollup index>>, or <<unfreeze-index-api,frozen>>.
 
+// TODO(pete): Figure out whether it's okay for this to point to the 'deleted pages' entry.
+
 * To drill down into the index
 <<mapping,mappings>>, <<index-modules-settings,settings>>, and statistics,
 click an index name. From this view, you can navigate to *Discover* to

docs/reference/indices/index-mgmt.asciidoc

@@ -160,6 +160,12 @@ https://www.elastic.co/blog/significantly-decrease-your-elasticsearch-heap-memor
 improvements in heap memory usage].
 // end::frozen-removal-explanation[]
 
+[role="exclude",id="unfreeze-index-api"]
+=== Unfreeze index API
+
+The unfreeze index API was removed in 9.0.
+include::redirects.asciidoc[tag=frozen-removal-explanation]
+
 [role="exclude",id="ilm-freeze"]
 === Freeze {ilm-init} action
 
@@ -1750,6 +1756,11 @@ See <<search-terms-enum>>.
 
 // tag::frozen-index-redirect[]
 
+// TODO(pete): Figure out what to do here. I don't think anything links here from main. But I guess users could get here
+// from link in old versions. Linking from here to the thing saying that the API isn't much use. Maybe we need a
+// sentence about what the feature was? And maybe the other places which currently point to unfreeze-index-api should
+// point here instead?
+
 For API documentation, see <<unfreeze-index-api>>.
 // end::frozen-index-redirect[]
 

docs/reference/redirects.asciidoc

@@ -103,6 +103,8 @@ requires the keyword `LIKE` for SQL `LIKE` pattern.
 By default, {es-sql} doesn't search <<unfreeze-index-api,frozen indices>>. To
 search frozen indices, use one of the following features:
 
+// TODO(pete): Figure out whether it's okay for this to point to the 'deleted pages' entry.
+
 dedicated configuration parameter::
 Set to `true` properties `index_include_frozen` in the <<sql-search-api,SQL search API>> or `index.include.frozen` in the drivers to include frozen indices.