Add migration documentation and update service account param

app/controllers/api/migrations.php

@@ -276,7 +276,7 @@ App::post('/v1/migrations/firebase')
     ->label('sdk.response.type', Response::CONTENT_TYPE_JSON)
     ->label('sdk.response.model', Response::MODEL_MIGRATION)
     ->param('resources', [], new ArrayList(new WhiteList(Firebase::getSupportedResources())), 'List of resources to migrate')
-    ->param('serviceAccount', '', new Text(512), "Source's Service Account")
+    ->param('serviceAccount', '', new Text(1024), "JSON of the Firebase service account credentials")
     ->inject('response')
     ->inject('dbForProject')
     ->inject('project')
@@ -326,7 +326,7 @@ App::get('/v1/migrations/firebase/report')
     ->label('sdk.response.type', Response::CONTENT_TYPE_JSON)
     ->label('sdk.response.model', Response::MODEL_MIGRATION_REPORT)
     ->param('resources', [], new ArrayList(new WhiteList(Firebase::getSupportedResources())), 'List of resources to migrate')
-    ->param('serviceAccount', '', new Text(512), "Source's Service Account")
+    ->param('serviceAccount', '', new Text(1024), "JSON of the Firebase service account credentials")
     ->param('databaseURL', '', new URL(), "Source's Database URL")
     ->inject('response')
     ->inject('dbForProject')

docs/references/migrations/delete-migration.md

@@ -0,0 +1 @@
+Delete a migration by its unique ID.

docs/references/migrations/get-migration.md

@@ -0,0 +1 @@
+Get a migration by its unique ID.

docs/references/migrations/list-migrations.md

@@ -0,0 +1 @@
+Get a list of all the project's migrations. You can use the query params to filter your results.

docs/references/migrations/migration-appwrite-report.md

@@ -0,0 +1 @@
+Perform permission checks and generate a report total data contained within a Appwrite instance including it's version number

docs/references/migrations/migration-appwrite.md

@@ -0,0 +1 @@
+Initialize a migration to transfer data from an Appwrite instance over to your current Appwrite instance. The migration will be queued and processed by the Appwrite server. To learn more about the migration process, please check out our [migration guide](/docs/migrations).

docs/references/migrations/migration-firebase-report.md

@@ -0,0 +1 @@
+Perform permission checks against a Firebase project to make sure migration is possible with the supplied credentials. This API does not return any data. It only checks the permissions.

docs/references/migrations/migration-firebase.md

@@ -0,0 +1 @@
+Initialize a migration to transfer data from an Firebase project over to your current Appwrite instance. The migration will be queued and processed by the Appwrite server. To learn more about the migration process, please check out our [migration guide](/docs/migrations).

docs/references/migrations/migration-nhost-report.md

@@ -0,0 +1 @@
+Perform permission checks and generate a report total data contained within a NHost instance

docs/references/migrations/migration-nhost.md

@@ -0,0 +1 @@
+Initialize a migration to transfer data from an NHost instance over to your current Appwrite instance. The migration will be queued and processed by the Appwrite server. To learn more about the migration process, please check out our [migration guide](/docs/migrations).

docs/references/migrations/migration-supabase-report.md

@@ -0,0 +1 @@
+Perform permission checks and generate a report total data contained within a Supabase instance

docs/references/migrations/migration-supabase.md

@@ -0,0 +1 @@
+Initialize a migration to transfer data from an Supabase instance over to your current Appwrite instance. The migration will be queued and processed by the Appwrite server. To learn more about the migration process, please check out our [migration guide](/docs/migrations).

docs/references/migrations/retry-migration.md

@@ -0,0 +1 @@
+Retry a migration by its unique ID. The migration status must be failed or aborted for the request to succeed.