fix more links

Author: taroface

src/current/_data/redirects.yml

@@ -303,14 +303,14 @@
   sources: ['import-data.md']
   versions: ['v2.1', 'v19.1', 'v19.2', 'v20.1', 'v20.2', 'v21.1']
 
-- destination: molt/molt-fetch.md
-  sources: [':version/molt-fetch.md']
-
 - destination: molt/migration-overview.md
   sources:
     - molt/live-migration-service.md
     - :version/live-migration-service.md
 
+- destination: molt/molt-fetch.md
+  sources: [':version/molt-fetch.md']
+
 - destination: molt/molt-verify.md
   sources: [':version/molt-verify.md']
 

src/current/_includes/molt/fetch-replication-output.md

@@ -12,7 +12,7 @@
 	{"level":"info","time":"2025-02-10T14:28:13-05:00","message":"staging database name: _replicator_1739215693817700000"}
 	~~~
 
-	The staging schema provides a replication marker for streaming changes. You will need the staging schema name in case replication fails and must be [resumed]({% link molt/molt-fetch.md %}#resume-replication), or [failback to the source database]({% link {{ site.current_cloud_version }}/migrate-failback.md %}) is performed.
+	The staging schema provides a replication marker for streaming changes. You will need the staging schema name in case replication fails and must be [resumed]({% link molt/molt-fetch.md %}#resume-replication), or [failback to the source database]({% link molt/migrate-failback.md %}) is performed.
 
 	`upserted rows` log messages indicate that changes were replicated to CockroachDB:
 

src/current/_includes/v23.1/sidebar-data/migrate.json

@@ -131,18 +131,6 @@
         }
       ]
     },
-    {
-      "title": "Migrate from PostgreSQL",
-      "urls": [
-        "/${VERSION}/migrate-from-postgres.html"
-      ]
-    },
-    {
-      "title": "Migrate from MySQL",
-      "urls": [
-        "/${VERSION}/migrate-from-mysql.html"
-      ]
-    },
     {
       "title": "Migrate from Oracle",
       "urls": [

src/current/_includes/v23.2/sidebar-data/migrate.json

@@ -137,18 +137,6 @@
         }
       ]
     },
-    {
-      "title": "Migrate from PostgreSQL",
-      "urls": [
-        "/${VERSION}/migrate-from-postgres.html"
-      ]
-    },
-    {
-      "title": "Migrate from MySQL",
-      "urls": [
-        "/${VERSION}/migrate-from-mysql.html"
-      ]
-    },
     {
       "title": "Migrate from Oracle",
       "urls": [

src/current/_includes/v24.1/sidebar-data/migrate.json

@@ -137,18 +137,6 @@
         }
       ]
     },
-    {
-      "title": "Migrate from PostgreSQL",
-      "urls": [
-        "/${VERSION}/migrate-from-postgres.html"
-      ]
-    },
-    {
-      "title": "Migrate from MySQL",
-      "urls": [
-        "/${VERSION}/migrate-from-mysql.html"
-      ]
-    },
     {
       "title": "Migrate from Oracle",
       "urls": [

src/current/_includes/v24.2/sidebar-data/migrate.json

@@ -137,18 +137,6 @@
         }
       ]
     },
-    {
-      "title": "Migrate from PostgreSQL",
-      "urls": [
-        "/${VERSION}/migrate-from-postgres.html"
-      ]
-    },
-    {
-      "title": "Migrate from MySQL",
-      "urls": [
-        "/${VERSION}/migrate-from-mysql.html"
-      ]
-    },
     {
       "title": "Migrate from Oracle",
       "urls": [

src/current/_includes/v24.3/sidebar-data/migrate.json

@@ -137,18 +137,6 @@
         }
       ]
     },
-    {
-      "title": "Migrate from PostgreSQL",
-      "urls": [
-        "/${VERSION}/migrate-from-postgres.html"
-      ]
-    },
-    {
-      "title": "Migrate from MySQL",
-      "urls": [
-        "/${VERSION}/migrate-from-mysql.html"
-      ]
-    },
     {
       "title": "Migrate from Oracle",
       "urls": [

src/current/molt/migrate-failback.md

@@ -10,7 +10,7 @@ Failback can be performed after you have loaded data into CockroachDB and are re
 {% assign tab_names_html = "Load and replicate;Phased migration;Failback" %}
 {% assign html_page_filenames = "migrate-to-cockroachdb.html;migrate-in-phases.html;migrate-failback.html" %}
 
-{% include filter-tabs.md tab_names=tab_names_html page_filenames=html_page_filenames page_folder=site.current_cloud_version %}
+{% include filter-tabs.md tab_names=tab_names_html page_filenames=html_page_filenames page_folder="molt" %}
 
 ## Before you begin
 
@@ -44,7 +44,7 @@ The following example watches the `employees` table for change events.
     Be mindful when specifying the connection strings: `--source` is the CockroachDB connection string and `--target` is the connection string of the database you migrated from.
     {{site.data.alerts.end}}
 
-    Use the `--stagingSchema` replication flag to provide the name of the staging schema. This is found in the `staging database name` message that is written at the beginning of the [replication task]({% link {{ site.current_cloud_version }}/migrate-in-phases.md %}#step-6-replicate-changes-to-cockroachdb).
+    Use the `--stagingSchema` replication flag to provide the name of the staging schema. This is found in the `staging database name` message that is written at the beginning of the [replication task]({% link molt/migrate-in-phases.md %}#step-6-replicate-changes-to-cockroachdb).
 
     <section class="filter-content" markdown="1" data-scope="postgres">
     {% include_cached copy-clipboard.html %}
@@ -116,5 +116,5 @@ The following example watches the `employees` table for change events.
 - [MOLT Fetch]({% link molt/molt-fetch.md %})
 - [MOLT Verify]({% link molt/molt-verify.md %})
 - [Migration Overview]({% link molt/migration-overview.md %})
-- [Migrate to CockroachDB]({% link {{ site.current_cloud_version }}/migrate-to-cockroachdb.md %})
-- [Migrate to CockroachDB in Phases]({% link {{ site.current_cloud_version }}/migrate-in-phases.md %})
+- [Migrate to CockroachDB]({% link molt/migrate-to-cockroachdb.md %})
+- [Migrate to CockroachDB in Phases]({% link molt/migrate-in-phases.md %})

src/current/molt/migrate-in-phases.md

@@ -10,7 +10,7 @@ A phased migration to CockroachDB uses the [MOLT tools]({% link molt/migration-o
 {% assign tab_names_html = "Load and replicate;Phased migration;Failback" %}
 {% assign html_page_filenames = "migrate-to-cockroachdb.html;migrate-in-phases.html;migrate-failback.html" %}
 
-{% include filter-tabs.md tab_names=tab_names_html page_filenames=html_page_filenames page_folder=site.current_cloud_version %}
+{% include filter-tabs.md tab_names=tab_names_html page_filenames=html_page_filenames page_folder="molt" %}
 
 ## Before you begin
 
@@ -140,7 +140,7 @@ The following example specifies that the `employees` table should be watched for
 1. Repeat [Step 4](#step-4-verify-the-data-load) to verify the updated data.
 
 {{site.data.alerts.callout_success}}
-If you encountered issues with replication, you can now use [`failback`]({% link {{ site.current_cloud_version }}/migrate-failback.md %}) mode to replicate changes on CockroachDB back to the initial source database. In case you need to roll back the migration, this ensures that data is consistent on the initial source database.
+If you encountered issues with replication, you can now use [`failback`]({% link molt/migrate-failback.md %}) mode to replicate changes on CockroachDB back to the initial source database. In case you need to roll back the migration, this ensures that data is consistent on the initial source database.
 {{site.data.alerts.end}}
 
 ## Step 8. Cutover
@@ -154,5 +154,5 @@ Perform a cutover by resuming application traffic, now to CockroachDB.
 - [MOLT Fetch]({% link molt/molt-fetch.md %})
 - [MOLT Verify]({% link molt/molt-verify.md %})
 - [Migration Overview]({% link molt/migration-overview.md %})
-- [Migrate to CockroachDB]({% link {{ site.current_cloud_version }}/migrate-to-cockroachdb.md %})
-- [Migration Failback]({% link {{ site.current_cloud_version }}/migrate-failback.md %})
+- [Migrate to CockroachDB]({% link molt/migrate-to-cockroachdb.md %})
+- [Migration Failback]({% link molt/migrate-failback.md %})

src/current/molt/migrate-to-cockroachdb.md

@@ -10,7 +10,7 @@ A migration to CockroachDB uses the [MOLT tools]({% link molt/migration-overview
 {% assign tab_names_html = "Load and replicate;Phased migration;Failback" %}
 {% assign html_page_filenames = "migrate-to-cockroachdb.html;migrate-in-phases.html;migrate-failback.html" %}
 
-{% include filter-tabs.md tab_names=tab_names_html page_filenames=html_page_filenames page_folder=site.current_cloud_version %}
+{% include filter-tabs.md tab_names=tab_names_html page_filenames=html_page_filenames page_folder="molt" %}
 
 ## Before you begin
 
@@ -96,7 +96,7 @@ Start the initial load of data into the target database. Continuous replication
 {% include molt/verify-output.md %}
 
 {{site.data.alerts.callout_success}}
-If you encountered issues with replication, you can now use [`failback`]({% link {{ site.current_cloud_version }}/migrate-failback.md %}) mode to replicate changes on CockroachDB back to the initial source database. In case you need to roll back the migration, this ensures that data is consistent on the initial source database.
+If you encountered issues with replication, you can now use [`failback`]({% link molt/migrate-failback.md %}) mode to replicate changes on CockroachDB back to the initial source database. In case you need to roll back the migration, this ensures that data is consistent on the initial source database.
 {{site.data.alerts.end}}
 
 ## Step 6. Modify the CockroachDB schema
@@ -114,5 +114,5 @@ Perform a cutover by resuming application traffic, now to CockroachDB.
 - [MOLT Fetch]({% link molt/molt-fetch.md %})
 - [MOLT Verify]({% link molt/molt-verify.md %})
 - [Migration Overview]({% link molt/migration-overview.md %})
-- [Migrate to CockroachDB in Phases]({% link {{ site.current_cloud_version }}/migrate-in-phases.md %})
-- [Migration Failback]({% link {{ site.current_cloud_version }}/migrate-failback.md %})
+- [Migrate to CockroachDB in Phases]({% link molt/migrate-in-phases.md %})
+- [Migration Failback]({% link molt/migrate-failback.md %})