Prepare for migration from /docs/latest to /latest (#10324) (#10395)

opensearch-trigger-bot[bot] · github-actions[bot] · peterzhuamazon · web-flow · commit b6ac7f8081e2 · 2025-07-24T14:55:21.000-04:00
* Prepare for migration from /docs/latest to /latest * Fix hardcoded link * Fix links * One more link fix * Update spec-insert to resolve the checks error --------- (cherry picked from commit 6f86f2b) Signed-off-by: Fanit Kolchina <kolchfa@amazon.com> Signed-off-by: Peter Zhu <zhujiaxi@amazon.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: Peter Zhu <zhujiaxi@amazon.com>
diff --git a/.github/vale/styles/OpenSearch/LinksExplicit.yml b/.github/vale/styles/OpenSearch/LinksExplicit.yml
@@ -5,4 +5,5 @@ nonword: true
 scope: raw
 tokens:
   - '\]\(https:\/\/www.opensearch.org\/docs\/latest'
-  
+  - '\]\(https:\/\/docs.opensearch.org\/docs\/latest'
+  - '\]\(https:\/\/docs.opensearch.org\/latest'
diff --git a/404.md b/404.md
@@ -8,12 +8,5 @@ nav_exclude: true
 
 ## Oops, this isn't the page you're looking for. 
 
-Maybe our [home page](https://opensearch.org/docs/latest) or one of the commonly visited pages below will help. If you need further support, please use the feedback feature on the right side of the screen to get in touch.
-
-- [Quickstart]({{site.url}}{{site.baseurl}}/quickstart/)
-- [Installing OpenSearch]({{site.url}}{{site.baseurl}}/install-and-configure/install-opensearch/index/)
-- [OpenSearch Dashboards]({{site.url}}{{site.baseurl}}/dashboards/index/)
-- [Query DSL]({{site.url}}{{site.baseurl}}/query-dsl/)
-- [API Reference]({{site.url}}{{site.baseurl}}/api-reference/index/)
-
+Maybe our [home page](https://docs.opensearch.org/latest/) or one of the commonly visited pages below will help. If you need further support, please use the feedback feature on the right side of the screen to get in touch.
 
diff --git a/API_STYLE_GUIDE.md b/API_STYLE_GUIDE.md
@@ -48,7 +48,7 @@ Provide an API name that describes its function, followed by a description of it
 Use sentence capitalization for the heading (for example, "Create or update mappings"). When you refer to the API operation, you can use lowercase with code font.
 
 If there is a corresponding OpenSearch Dashboards feature, provide a “See also” link that references it. 
-*Example*: “To learn more about monitor findings, see [Document findings](https://opensearch.org/docs/latest/monitoring-plugins/alerting/monitors/#document-findings)."
+*Example*: “To learn more about monitor findings, see [Document findings](https://docs.opensearch.org/latest/monitoring-plugins/alerting/monitors/#document-findings)."
 
 If applicable, provide any caveats to its usage with a note or tip, as in the following example:
 
diff --git a/DEVELOPER_GUIDE.md b/DEVELOPER_GUIDE.md
@@ -11,7 +11,7 @@
 
 ## Introduction
 
-The `.md` documents in this repository are rendered into HTML pages using [Jekyll](https://jekyllrb.com/). These HTML pages are hosted on [opensearch.org](https://opensearch.org/docs/latest/).
+The `.md` documents in this repository are rendered into HTML pages using [Jekyll](https://jekyllrb.com/). These HTML pages are hosted on [opensearch.org](https://docs.opensearch.org/latest/).
 
 ## Starting the Jekyll server locally
 
diff --git a/STYLE_GUIDE.md b/STYLE_GUIDE.md
@@ -51,7 +51,7 @@ Use lowercase when referring to features, unless you are referring to a formally
 
 A plugin is a feature or distinct component that extends the functionality of OpenSearch. For now, capitalize plugin names, but use *plugin* sparingly. The concept of plugins will become obsolete once we re-architect the product. For example:
 
-* "Interaction with the *ML Commons* plugin occurs through either the REST API or [ad](https://opensearch.org/docs/latest/search-plugins/sql/ppl/functions#ad) and [kmeans](https://opensearch.org/docs/latest/search-plugins/sql/ppl/functions#kmeans) Piped Processing Language (PPL) commands."
+* "Interaction with the *ML Commons* plugin occurs through either the REST API or [ad](https://docs.opensearch.org/latest/search-plugins/sql/ppl/functions#ad) and [kmeans](https://docs.opensearch.org/latest/search-plugins/sql/ppl/functions#kmeans) Piped Processing Language (PPL) commands."
 * "Use the *Neural Search* plugin to integrate ML language models into your search workloads."
 
 ### Voice and tone
@@ -263,7 +263,7 @@ When introducing a code or command line example that refers to a variable or pla
           - Where space is limited (for example, in a table), you can use "*See* [link text]."
      - Ensure that the link text matches the section title text. <br> <br> Example: "To get involved, see [Contributing](https://opensearch.org/source.html) on the OpenSearch website." <br>
 
-- **Embedded links**: Embedded links are woven into a sentence without formal introductory text. They're especially useful in tables or other elements where space is tight. The text around the embedded link must relate to the information in the link so that the reader understands the context. Do not use *here* or *click here* for link text because it creates accessibility problems. <br> <br> Example: "Finally, [delete the index](https://opensearch.org/docs/latest/api-reference/index-apis/delete-index)."
+- **Embedded links**: Embedded links are woven into a sentence without formal introductory text. They're especially useful in tables or other elements where space is tight. The text around the embedded link must relate to the information in the link so that the reader understands the context. Do not use *here* or *click here* for link text because it creates accessibility problems. <br> <br> Example: "Finally, [delete the index](https://docs.opensearch.org/latest/api-reference/index-apis/delete-index)."
 
 ### Lists
 
diff --git a/_config.yml b/_config.yml
@@ -1,8 +1,8 @@
 title: OpenSearch Documentation
 description: >- # this means to ignore newlines until "baseurl:"
   Documentation for OpenSearch, the Apache 2.0 search, analytics, and visualization suite with advanced security, alerting, SQL support, automated index management, deep performance analysis, and more.
-baseurl: "/docs/latest" # The subpath of the current version. This is version-specific. For example, for 2.19, the base URL is /docs/2.19.
-latesturl: "/docs/latest" # The subpath of the latest version. Used for non-version-specific documentation, like Data Prepper, etc.
+baseurl: "/latest" # The subpath of the current version. This is version-specific. For example, for 2.19, the base URL is /docs/2.19.
+latesturl: "/latest" # The subpath of the latest version. Used for non-version-specific documentation, like Data Prepper, etc.
 url: "https://docs.opensearch.org" # the base hostname & protocol for your site, e.g. http://example.com
 permalink: /:path/
 
diff --git a/_data/migration-assistant/breaking-changes.yml b/_data/migration-assistant/breaking-changes.yml
@@ -22,22 +22,22 @@ breaking_changes:
     introducedIn: "OpenSearch 1.x"
     comp: []
   - title: "OpenSearch 2.x: Remove mapping types parameter"
-    url: "https://docs.opensearch.org/docs/latest/breaking-changes/#remove-mapping-types-parameter"
+    url: "https://docs.opensearch.org/latest/breaking-changes/#remove-mapping-types-parameter"
     introducedIn: "OpenSearch 2.x"
     comp: []
     transformation:
       title: "Type Mapping Deprecation"
-      url: "https://docs.opensearch.org/docs/latest/migration-assistant/migration-phases/planning-your-migration/handling-type-mapping-deprecation/"
+      url: "https://docs.opensearch.org/latest/migration-assistant/migration-phases/planning-your-migration/handling-type-mapping-deprecation/"
   - title: "OpenSearch 3.x: Breaking Changes"
-    url: "/docs/latest/breaking-changes/#300"
+    url: "https://docs.opensearch.org/latest/breaking-changes/#300"
     introducedIn: "OpenSearch 3.x"
     comp: []
   - title: "OpenSearch Notifications Plugins"
-    url: "https://docs.opensearch.org/docs/latest/breaking-changes/#add-opensearch-notifications-plugins"
+    url: "https://docs.opensearch.org/latest/breaking-changes/#add-opensearch-notifications-plugins"
     introducedIn: "OpenSearch 2.x"
     comp: []
   - title: "OpenSearch 2.x: Client JDK 8 Support Dropped"
-    url: "https://docs.opensearch.org/docs/latest/breaking-changes/#drop-support-for-jdk-8"
+    url: "https://docs.opensearch.org/latest/breaking-changes/#drop-support-for-jdk-8"
     introducedIn: "OpenSearch 2.x"
     comp: []
   - title: "Removal of Types in Elasticsearch 7.x"
@@ -46,7 +46,7 @@ breaking_changes:
     comp: []
     transformation:
       title: "Type Mapping Deprecation"
-      url: "https://docs.opensearch.org/docs/latest/migration-assistant/migration-phases/planning-your-migration/handling-type-mapping-deprecation/"
+      url: "https://docs.opensearch.org/latest/migration-assistant/migration-phases/planning-your-migration/handling-type-mapping-deprecation/"
   - title: "Elasticsearch 6.0 - 6.6 Breaking Changes"
     url: "https://www.elastic.co/guide/en/elasticsearch/reference/6.8/breaking-changes.html"
     introducedIn: "Elasticsearch 6.x"
diff --git a/_data/top_nav.yml b/_data/top_nav.yml
@@ -40,18 +40,18 @@ items:
       - label: Members
         url: https://opensearch.org/authors-list/
   - label: Documentation
-    url: https://docs.opensearch.org/docs/latest/
+    url: https://docs.opensearch.org/latest/
     children:
       - label: OpenSearch and Dashboards
-        url: https://docs.opensearch.org/docs/latest/about/
+        url: https://docs.opensearch.org/latest/about/
       - label: Data Prepper
-        url: https://docs.opensearch.org/docs/latest/data-prepper/
+        url: https://docs.opensearch.org/latest/data-prepper/
       - label: Clients
-        url: https://docs.opensearch.org/docs/latest/clients/
+        url: https://docs.opensearch.org/latest/clients/
       - label: Benchmark
-        url: https://docs.opensearch.org/docs/latest/benchmark/
+        url: https://docs.opensearch.org/latest/benchmark/
       - label: Migration Assistant
-        url: https://docs.opensearch.org/docs/latest/migration-assistant/
+        url: https://docs.opensearch.org/latest/migration-assistant/
   - label: Blog
     url: https://opensearch.org/blog/
   - label: Download
diff --git a/_migration-assistant/overview/architecture.md b/_migration-assistant/overview/architecture.md
@@ -19,6 +19,6 @@ Each node in the diagram correlates to the following steps in the migration proc
 2. An Application Load Balancer with capture proxies relays traffic to a source while replicating data to Amazon Managed Streaming for Apache Kafka (Amazon MSK).
 3. Using the migration console, you can initiate metadata migration to establish indexes, templates, component templates, and aliases on the target cluster.
 4. With continuous traffic capture in place, you can use a `reindex-from-snapshot` process to capture data from your current index.
-5. Once `Reindex-from-Snapshot` is complete, captured traffic is replayed from Amazon MSK to the target cluster by [Traffic Replayer](https://docs.opensearch.org/docs/latest/migration-assistant/migration-phases/live-traffic-migration/using-traffic-replayer/).
+5. Once `Reindex-from-Snapshot` is complete, captured traffic is replayed from Amazon MSK to the target cluster by [Traffic Replayer]({{site.url}}{{site.baseurl}}/migration-assistant/migration-phases/live-traffic-migration/using-traffic-replayer/).
 6. Performance and behavior of traffic sent to the source and target clusters are compared by reviewing logs and metrics.
 7. After confirming that the target cluster's functionality meets expectations, clients are redirected to the new target.
diff --git a/_migration-assistant/overview/key-components.md b/_migration-assistant/overview/key-components.md
@@ -23,7 +23,7 @@ This component is designed for HTTP RESTful traffic. It forwards traffic to the
 
 ## Traffic Replayer
 
-Acting as a traffic simulation tool, [Traffic Replayer](https://docs.opensearch.org/docs/latest/migration-assistant/migration-phases/live-traffic-migration/using-traffic-replayer/) replays recorded request traffic to a target cluster, mirroring source traffic patterns. It links original requests and their responses to those directed at the target cluster, facilitating comparative analysis.
+Acting as a traffic simulation tool, [Traffic Replayer]({{site.url}}{{site.baseurl}}/migration-assistant/migration-phases/live-traffic-migration/using-traffic-replayer/) replays recorded request traffic to a target cluster, mirroring source traffic patterns. It links original requests and their responses to those directed at the target cluster, facilitating comparative analysis.
 
 ## Metadata migration tool
 
diff --git a/_query-dsl/full-text/simple-query-string.md b/_query-dsl/full-text/simple-query-string.md
@@ -359,7 +359,7 @@ Parameter | Data type | Description
 `auto_generate_synonyms_phrase_query` | Boolean | Specifies whether to create [match_phrase queries]({{site.url}}{{site.baseurl}}/query-dsl/full-text/match/) automatically for multi-term synonyms. Default is `true`.
 `default_operator`| String | If the query string contains multiple search terms, whether all terms need to match (`AND`) or only one term needs to match (`OR`) for a document to be considered a match. Valid values are:<br>- `OR`: The string `to be` is interpreted as `to OR be`<br>- `AND`: The string `to be` is interpreted as `to AND be`<br> Default is `OR`.
 `fields` | String array | The list of fields to search (for example, `"fields": ["title^4", "description"]`). Supports wildcards. If unspecified, defaults to the `index.query.default_field` setting, which defaults to `["*"]`. The maximum number of fields that can be searched at the same time is defined by `indices.query.bool.max_clause_count`, which is 1,024 by default.
-`flags` | String | A `|`-delimited string of [flags]({{site.baseurl}}/query-dsl/full-text/simple-query-string/) to enable (for example, `AND|OR|NOT`). Default is `ALL`. You can explicitly set the value for `default_field`. For example, to return all titles, set it to `"default_field": "title"`.
+`flags` | String | A `|`-delimited string of [flags](#limit-operators) to enable (for example, `AND|OR|NOT`). Default is `ALL`. You can explicitly set the value for `default_field`. For example, to return all titles, set it to `"default_field": "title"`.
 `fuzzy_max_expansions` | Positive integer | The maximum number of terms to which the query can expand. Fuzzy queries “expand to” a number of matching terms that are within the distance specified in `fuzziness`. Then OpenSearch tries to match those terms. Default is `50`.
 `fuzzy_transpositions` | Boolean | Setting `fuzzy_transpositions` to `true` (default) adds swaps of adjacent characters to the insert, delete, and substitute operations of the `fuzziness` option. For example, the distance between `wind` and `wnid` is 1 if `fuzzy_transpositions` is true (swap "n" and "i") and 2 if it is false (delete "n", insert "n"). If `fuzzy_transpositions` is false, `rewind` and `wnid` have the same distance (2) from `wind`, despite the more human-centric opinion that `wnid` is an obvious typo. The default is a good choice for most use cases.
 `fuzzy_prefix_length`| Integer | The number of beginning characters left unchanged for fuzzy matching. Default is 0. 
diff --git a/_search-plugins/sql/full-text.md b/_search-plugins/sql/full-text.md
@@ -150,7 +150,7 @@ You can specify the following options for `MULTI_MATCH` in any order:
 - `zero_terms_query`
 - `boost`
 
-Refer to `multi_match` query [documentation]({{site.baseurl}}/query-dsl/full-text/multi-match/) for parameter description and supported values.
+Refer to `multi_match` query [documentation]({{site.url}}{{site.baseurl}}/query-dsl/full-text/multi-match/) for parameter description and supported values.
 
 ### For example, REST API search for `Dale` in either the `firstname` or `lastname` fields:
 
diff --git a/_security/access-control/api.md b/_security/access-control/api.md
@@ -951,7 +951,7 @@ The `hosts` parameter maps requests originating from specific IP addresses or ho
   opensearch_security.host_resolver_mode: ip-hostname
   ```
 
-  This enables reverse DNS lookups to resolve hostnames. For more information, see [Configuring OpenSearch](https://docs.opensearch.org/docs/latest/install-and-configure/configuring-opensearch/index/).
+  This enables reverse DNS lookups to resolve hostnames. For more information, see [Configuring OpenSearch]({{site.url}}{{site.baseurl}}/install-and-configure/configuring-opensearch/index/).
 
 Using `"*"` in `hosts` matches all client IPs and hostnames, meaning this role will be applied to every request, regardless of user. This can unintentionally overgrant access if used alongside `users: ["someuser"]`. Avoid setting `hosts: ["*"]` unless you're intentionally granting the role to all client IPs.
 {: .warning}
diff --git a/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md b/_tuning-your-cluster/availability-and-recovery/segment-replication/index.md
@@ -8,6 +8,7 @@ datatable: true
 redirect_from:
   - /opensearch/segment-replication/
   - /opensearch/segment-replication/index/
+  - /tuning-your-cluster/segment-replication/
 ---
 
 # Segment replication
@@ -401,7 +402,7 @@ The following table lists benchmarking results for the `stackoverflow` dataset f
 
 As the number of replicas increases, the amount of time required for primary shards to keep replicas up to date (known as the _replication lag_) also increases. This is because segment replication copies the segment files directly from primary shards to replicas. 
 
-The benchmarking results show a non-zero error rate as the number of replicas increases. The error rate indicates that the [segment replication backpressure]({{site.urs}}{{site.baseurl}}/tuning-your-cluster/availability-and-recovery/segment-replication/backpressure/) mechanism is initiated when replicas cannot keep up with the primary shard. However, the error rate is offset by the significant CPU and memory gains that segment replication provides.
+The benchmarking results show a non-zero error rate as the number of replicas increases. The error rate indicates that the [segment replication backpressure]({{site.url}}{{site.baseurl}}/tuning-your-cluster/availability-and-recovery/segment-replication/backpressure/) mechanism is initiated when replicas cannot keep up with the primary shard. However, the error rate is offset by the significant CPU and memory gains that segment replication provides.
 
 ## Next steps
 
diff --git a/assets/js/_version-selector.js b/assets/js/_version-selector.js
@@ -191,10 +191,10 @@ class VersionSelector extends HTMLElement {
 
         frag.querySelector('#selected').textContent = `${PREFIX}${this.getAttribute('selected')}`;
 
-        const pathName = location.pathname.replace(/\/docs(\/((latest|\d+\.\d+)\/?)?)?/, '');
+        const pathName = location.pathname.replace(/\/(docs)?(\/((latest|\d+\.\d+)\/?)?)?/, '');
         const versionsDOMNodes = DOC_VERSIONS.map((v, idx) => v === DOC_VERSION_LATEST
-          ? `<a href="/docs/latest/${pathName}" class="latest">${PREFIX}${v}</a>`
-          : `<a href="/docs/${v}/${pathName}">${PREFIX}${v}</a>`,
+        ? `<a href="/latest/${pathName}" class="latest">${PREFIX}${v}</a>`
+        : `<a href="/${v}/${pathName}">${PREFIX}${v}</a>`,
         );
         if (Array.isArray(DOC_VERSIONS_ARCHIVED) && DOC_VERSIONS_ARCHIVED.length) {
             versionsDOMNodes.push(
diff --git a/spec-insert/config.yml b/spec-insert/config.yml
@@ -9,7 +9,7 @@ param_table:
 
 # Replace text in every description in the spec file
 text_replacements:
-  - replace: "https://opensearch.org/docs/latest"
+  - replace: "https://docs.opensearch.org/latest"
     with: "{{site.url}}{{site.baseurl}}"
   - replace: "\n"
     with: " "
diff --git a/spec-insert/lib/doc_processor.rb b/spec-insert/lib/doc_processor.rb
@@ -46,7 +46,7 @@ def find_insertions(lines)
                          .filter { |line, _index| line.match?(START_MARKER) }
                          .map { |_line, index| index }
     end_indices = start_indices.map do |index|
-      (index..lines.length - 1).find { |i| lines[i].match?(END_MARKER) }
+      (index..(lines.length - 1)).find { |i| lines[i].match?(END_MARKER) }
     end.compact
 
     validate_markers!(start_indices, end_indices)
diff --git a/spec-insert/lib/renderers/path_parameters.rb b/spec-insert/lib/renderers/path_parameters.rb
@@ -11,7 +11,7 @@ def table
     ParameterTableRenderer.new(params, @args).render
   end
 
-  def optional
+  def optional?
     params.none?(&:required)
   end
 
diff --git a/spec-insert/lib/renderers/query_parameters.rb b/spec-insert/lib/renderers/query_parameters.rb
@@ -11,7 +11,7 @@ def table
     ParameterTableRenderer.new(params, @args).render
   end
 
-  def optional
+  def optional?
     params.none?(&:required)
   end
 
diff --git a/spec-insert/lib/reports/dry_run_report.rb b/spec-insert/lib/reports/dry_run_report.rb
@@ -17,7 +17,7 @@ def initialize
     generate_dry_runs
   end
 
-  def any_errors
+  def any_errors?
     @errors_report.keys.any?
   end
 
diff --git a/spec-insert/spec/_fixtures/expected_output/url_params_tables.md b/spec-insert/spec/_fixtures/expected_output/url_params_tables.md
@@ -6,7 +6,7 @@ component: path_parameters
 -->
 ## Path parameters
 
-The following table lists the available path parameters. All path parameters are optional.
+The following table lists the available path parameters.
 
 | Parameter | Data type | Description |
 | :--- | :--- | :--- |
diff --git a/spec-insert/spec/_fixtures/opensearch_spec.yaml b/spec-insert/spec/_fixtures/opensearch_spec.yaml
diff --git a/spec-insert/spec/mock_config.yml b/spec-insert/spec/mock_config.yml
