Skip to content

Commit 6881fc6

Browse files
Fix broken external link hash in guiding-principles page
CI validate_html_output task fails because html-proofer can't find the #fix-cluster-status-recover-nodes hash on the Elastic docs page. The page generates anchor IDs via client-side JavaScript, which html-proofer doesn't execute. The link works fine in browsers. Drop the hash fragment from the URL. The link still points to the correct page about fixing red/yellow cluster status, and the 'Recover lost nodes' section is prominent on that page.
1 parent 533345f commit 6881fc6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

config/site/src/guides/guiding-principles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ These are the "north stars" that guide ElasticGraph development. They guide the
5252
that the data in your index might "regress" to a prior state.
5353
* It makes it easy to operate multiple ElasticGraph instances (e.g. each in a different AWS region) which are guaranteed to
5454
converge on the same indexed state. (This is how we recommend deploying ElasticGraph for projects that require high availability.)
55-
* It allows you to recover from a [red OpenSearch or Elasticsearch cluster](https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html#fix-cluster-status-recover-nodes)
55+
* It allows you to recover from a [red OpenSearch or Elasticsearch cluster](https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html)
5656
by restoring from a snapshot and playing back the indexing events after the snapshot was taken--this is guaranteed to converge
5757
on the indexed state you started with.
5858

0 commit comments

Comments
 (0)