chore: update live migration docs to v0.0.16

Signed-off-by: Harkishen-Singh <harkishensingh@hotmail.com>

_partials/_migrate_live_migration_cleanup.md

@@ -6,7 +6,7 @@ docker run --rm -it --name live-migration-clean \
     -e PGCOPYDB_TARGET_PGURI=$TARGET \
     --pid=host \
     -v ~/live-migration:/opt/timescale/ts_cdc \
-    timescale/live-migration:v0.0.15 clean --prune
+    timescale/live-migration:v0.0.16 clean --prune
 ```
 
 The `--prune` flag is used to delete temporary files in the `~/live-migration` directory

_partials/_migrate_live_migration_docker_subcommand.md

@@ -6,7 +6,7 @@ docker run --rm -it --name live-migration \
     -e PGCOPYDB_TARGET_PGURI=$TARGET \
     --pid=host \
     -v ~/live-migration:/opt/timescale/ts_cdc \
-    timescale/live-migration:v0.0.15 --help
+    timescale/live-migration:v0.0.16 --help
 
 Live migration moves your PostgreSQL/TimescaleDB to Timescale Cloud with minimal downtime.
 
@@ -53,7 +53,7 @@ docker run --rm -it --name live-migration-snapshot \
     -e PGCOPYDB_TARGET_PGURI=$TARGET \
     --pid=host \
     -v ~/live-migration:/opt/timescale/ts_cdc \
-    timescale/live-migration:v0.0.15 snapshot
+    timescale/live-migration:v0.0.16 snapshot
 ```
 
 In addition to creating a snapshot, this process also validates prerequisites on the source and target to ensure the database instances are ready for replication.
@@ -69,7 +69,36 @@ Press 'c' and ENTER to continue
 
 ### 3.b Perform live-migration
 
-Next, open a new terminal and initiate the live migration. Allow it to
+The `migrate` subcommand supports following flags
+
+```sh
+docker run --rm -it --name live-migration-migrate \
+    -e PGCOPYDB_SOURCE_PGURI=$SOURCE \
+    -e PGCOPYDB_TARGET_PGURI=$TARGET \
+    --pid=host \
+    -v ~/live-migration:/opt/timescale/ts_cdc \
+    timescale/live-migration:v0.0.16 migrate --help
+usage: main.py migrate [-h] [--dir DIR] [--resume] [--skip-roles] [--table-jobs TABLE_JOBS] [--index-jobs INDEX_JOBS]
+                       [--skip-extensions [SKIP_EXTENSIONS ...]] [--skip-table-data SKIP_TABLE_DATA [SKIP_TABLE_DATA ...]]
+
+options:
+  -h, --help            Show this help message and exit
+  --resume              Resume the migration
+  --skip-roles          Skip roles migration
+  --table-jobs TABLE_JOBS
+                        Number of parallel jobs to copy "existing data" from source db to target db (Default: 8)
+  --index-jobs INDEX_JOBS
+                        Number of parallel jobs to create indexes in target db (Default: 8)
+  --skip-extensions [SKIP_EXTENSIONS ...]
+                        Skips the given extensions during migration. Empty list skips all extensions.
+  --skip-table-data SKIP_TABLE_DATA [SKIP_TABLE_DATA ...]
+                        Skips data from the given table during migration. However, the table schema will be migrated. To skip data from a
+                        Hypertable, you will need to specify a list of schema qualified chunks belonging to the Hypertable. Currently, this
+                        flag does not skip data during live replay from the specified table. Values for this flag must be schema qualified. Eg:
+                        --skip-table-data public.exclude_table_1 public.exclude_table_2
+```
+
+Next, we will start the migration process. Open a new terminal and initiate the live migration, and allow it to
 run uninterrupted.
 
 ```sh
@@ -78,7 +107,7 @@ docker run --rm -it --name live-migration-migrate \
     -e PGCOPYDB_TARGET_PGURI=$TARGET \
     --pid=host \
     -v ~/live-migration:/opt/timescale/ts_cdc \
-    timescale/live-migration:v0.0.15 migrate
+    timescale/live-migration:v0.0.16 migrate
 ```
 <Highlight type="note">
 If the migrate command stops for any reason during execution, you can resume

migrate/live-migration/live-migration-faq.md

@@ -110,3 +110,5 @@ No, Timescale Cloud cannot be used as a source database for live migration.
 
 At present, live migration does not allow for excluding schemas or tables from
 replication, but this feature is expected to be added in future releases.
+However, a workaround is available for skipping table data using the `--skip-table-data` flag.
+For more information, please refer to the help text under the `migrate` subcommand.