Replaced extracting JAR content with the migration links.

Author: vnandwana

userguide/aviate/aviate-database-migrations.adoc

@@ -130,54 +130,13 @@ If the schema already exists, Flyway must be aligned with the current database s
 
 ===== Step 1 — Retrieve the Migration Files
 
-Migration scripts are packaged inside each Aviate plugin JAR.
+Download the migration scripts from the following link:
 
-If you already know which Aviate plugin version created the schema, download that exact version:
+MySQL migrations:
+https://docs.killbill.io/latest/aviate-migrations/mysql/
 
-----
-curl -O "https://dl.cloudsmith.io/<token>/killbill/aviate/maven/com/kill-bill/billing/plugin/java/aviate-plugin/<version>/aviate-plugin-<version>.jar"
-----
-
-Otherwise, use the latest plugin version available on the Kill Bill node.
-
-The plugin directory is controlled by:
-
-----
-org.killbill.billing.plugin.kpm.bundlesPath
-----
-
-Default location:
-
-----
-/var/lib/killbill/bundles
-----
-
-Example:
-
-----
-/var/lib/killbill/bundles/plugins/java/aviate-plugin/
-├── 1.0.28
-├── 1.0.29
-└── SET_DEFAULT
-----
-
-Each version contains a plugin JAR: `aviate-plugin-<version>.jar`
-
-Select the version whose migrations most closely match the existing database schema.
-
-Extract the plugin JAR:
-----
-unzip aviate-plugin-1.0.29.jar -d aviate-plugin-1.0.29
-----
-
-Then inspect:
-----
-db/migration/mysql
-
-or
-
-db/migration/postgresql
-----
+PostgreSQL migrations:
+https://docs.killbill.io/latest/aviate-migrations/postgresql/
 
 Migration files follow the following format:
 
@@ -187,7 +146,7 @@ aviateV1.2.0__catalog_usage.sql
 aviateV1.3.0__catalog_meter.sql
 ----
 
-The last migration file represents the schema version created by that plugin release.
+After downloading, compare the migration files with your current Aviate schema to identify the latest version already reflected in your database. This version will be used as the Flyway baseline.
 
 Example:
 
@@ -393,29 +352,13 @@ Note the migration version where `success = 0`.
 
 Review the migration script referenced in the error logs.
 
-Migration scripts are packaged inside the Aviate plugin JAR.
+Download the migration scripts from the following link:
 
-Locate the plugin directory (see the value of `org.killbill.billing.plugin.kpm.bundlesPath` property), by default its at the following location:
+MySQL migrations:
+https://docs.killbill.io/latest/aviate-migrations/mysql/
 
-----
-/var/lib/killbill/bundles/plugins/java/aviate-plugin/<version>/
-----
-
-Extract the JAR:
-
-----
-unzip aviate-plugin-<version>.jar -d aviate-plugin
-----
-
-Then navigate to:
-
-----
-db/migration/mysql
-
-or
-
-db/migration/postgresql
-----
+PostgreSQL migrations:
+https://docs.killbill.io/latest/aviate-migrations/postgresql/
 
 Open the migration file mentioned in the logs to understand what schema changes were attempted.
 
@@ -526,31 +469,15 @@ Unknown column 'kb_account_id'
 
 This indicates that the migration responsible for adding this column was never applied or was reverted.
 
-===== Step 2 — Locate the Migration Script
+===== Step 2 — Check the Migration Script
 
-Migration scripts are packaged inside the Aviate plugin JAR.
+Download the migration scripts from the following link:
 
-Locate the plugin directory:
+MySQL migrations:
+https://docs.killbill.io/latest/aviate-migrations/mysql/
 
-----
-/var/lib/killbill/bundles/plugins/java/aviate-plugin/<version>/
-----
-
-Extract the JAR:
-
-----
-unzip aviate-plugin-<version>.jar -d aviate-plugin
-----
-
-Then navigate to:
-
-----
-db/migration/mysql
-
-or
-
-db/migration/postgresql
-----
+PostgreSQL migrations:
+https://docs.killbill.io/latest/aviate-migrations/postgresql/
 
 Locate the migration file referenced in the error logs and review it to determine which column, table, or object is missing from the schema.