@omnibase/core-js 0.9.13 → 0.9.15

package/src/models/index.ts

@@ -1,6 +1,7 @@
 /* tslint:disable */
 /* eslint-disable */
 export * from './AcceptInvite200Response';
+export * from './AddSubscription200Response';
 export * from './ApiV1StorageDownloadPost200Response';
 export * from './ApiV1StorageObjectDelete200Response';
 export * from './ApiV1StorageUploadPost200Response';
@@ -17,17 +18,25 @@ export * from './ClientSessionAuthenticationMethod';
 export * from './ClientSessionDevice';
 export * from './ClientSubjectSet';
 export * from './ClientVerifiableIdentityAddress';
+export * from './ConvertStripeIDToConfigID200Response';
 export * from './CreateCheckout200Response';
 export * from './CreateCustomerPortal200Response';
 export * from './CreateInvite200Response';
+export * from './CreateOrUpdateEmailTemplate200Response';
+export * from './CreateOrUpdateEmailTemplate200ResponseAllOfData';
 export * from './CreateRelationship200Response';
 export * from './CreateRole200Response';
 export * from './CreateSubscription200Response';
 export * from './CreateTenant200Response';
+export * from './DeleteEmailTemplate200Response';
+export * from './DeleteEmailTemplate200ResponseAllOfData';
 export * from './DeleteRole200Response';
 export * from './DeleteTenant200Response';
 export * from './DeployPermissionNamespaces200Response';
 export * from './GetActiveTenant200Response';
+export * from './GetEmailTemplateByType200Response';
+export * from './GetEmailTemplates200Response';
+export * from './GetEmailTemplates200ResponseAllOfData';
 export * from './GetIdentity200Response';
 export * from './GetRoleDefinitions200Response';
 export * from './GetSession200Response';
@@ -51,6 +60,7 @@ export * from './ModelsBillingStatusResponse';
 export * from './ModelsDeleteObjectRequest';
 export * from './ModelsDownloadRequest';
 export * from './ModelsDownloadResponse';
+export * from './ModelsEmailTemplate';
 export * from './ModelsListTenantsResponse';
 export * from './ModelsLogoutResponse';
 export * from './ModelsMessageResponse';
@@ -86,6 +96,8 @@ export * from './RemoveSubscription200Response';
 export * from './SwitchActiveTenant200Response';
 export * from './TenantsAcceptInviteRequest';
 export * from './TenantsAcceptInviteResponse';
+export * from './TenantsAddSubscriptionRequest';
+export * from './TenantsAddSubscriptionResponse';
 export * from './TenantsAssignRoleRequest';
 export * from './TenantsAssignRoleResponse';
 export * from './TenantsCreateRoleRequest';
@@ -118,6 +130,7 @@ export * from './V1ConfigHistoryPagination';
 export * from './V1ConfigHistoryResponse';
 export * from './V1CreateCheckoutRequest';
 export * from './V1CreateCheckoutResponse';
+export * from './V1CreateEmailTemplateRequest';
 export * from './V1CreatePortalRequest';
 export * from './V1CreatePortalResponse';
 export * from './V1CreateRelationshipRequest';
@@ -127,5 +140,6 @@ export * from './V1MigrationSuccessResponse';
 export * from './V1NamespaceDeploymentResponse';
 export * from './V1RecordUsageRequest';
 export * from './V1StripeConfigResponse';
+export * from './V1StripeIDConversionResponse';
 export * from './V1SubjectSetRequest';
 export * from './WhoAmI200Response';

package/src/runtime.ts

@@ -4,7 +4,7 @@
  * Omnibase REST API
  * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
  *
- * The version of the OpenAPI document: 0.9.13
+ * The version of the OpenAPI document: 0.9.15
  * Contact: support@omnibase.dev
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/apis/V1DatabaseApi.d.ts

@@ -1,31 +0,0 @@
-/**
- * Omnibase REST API
- * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
- *
- * The version of the OpenAPI document: 0.9.13
- * Contact: support@omnibase.dev
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-import * as runtime from '../runtime';
-import type { V1MigrationSuccessResponse } from '../models/index';
-export interface UploadDatabaseMigrationsRequest {
-    migrations: Blob;
-}
-/**
- *
- */
-export declare class V1DatabaseApi extends runtime.BaseAPI {
-    /**
-     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-     * Upload database migrations
-     */
-    uploadDatabaseMigrationsRaw(requestParameters: UploadDatabaseMigrationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V1MigrationSuccessResponse>>;
-    /**
-     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-     * Upload database migrations
-     */
-    uploadDatabaseMigrations(requestParameters: UploadDatabaseMigrationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V1MigrationSuccessResponse>;
-}

package/dist/apis/V1DatabaseApi.js

@@ -1,86 +0,0 @@
-"use strict";
-/* tslint:disable */
-/* eslint-disable */
-/**
- * Omnibase REST API
- * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
- *
- * The version of the OpenAPI document: 0.9.13
- * Contact: support@omnibase.dev
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
-    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
-    return new (P || (P = Promise))(function (resolve, reject) {
-        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
-        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
-        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
-        step((generator = generator.apply(thisArg, _arguments || [])).next());
-    });
-};
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.V1DatabaseApi = void 0;
-const runtime = require("../runtime");
-const index_1 = require("../models/index");
-/**
- *
- */
-class V1DatabaseApi extends runtime.BaseAPI {
-    /**
-     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-     * Upload database migrations
-     */
-    uploadDatabaseMigrationsRaw(requestParameters, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters['migrations'] == null) {
-                throw new runtime.RequiredError('migrations', 'Required parameter "migrations" was null or undefined when calling uploadDatabaseMigrations().');
-            }
-            const queryParameters = {};
-            const headerParameters = {};
-            if (this.configuration && this.configuration.apiKey) {
-                headerParameters["Authorization"] = yield this.configuration.apiKey("Authorization"); // BearerAuth authentication
-            }
-            const consumes = [
-                { contentType: 'multipart/form-data' },
-            ];
-            // @ts-ignore: canConsumeForm may be unused
-            const canConsumeForm = runtime.canConsumeForm(consumes);
-            let formParams;
-            let useForm = false;
-            // use FormData to transmit files using content-type "multipart/form-data"
-            useForm = canConsumeForm;
-            if (useForm) {
-                formParams = new FormData();
-            }
-            else {
-                formParams = new URLSearchParams();
-            }
-            if (requestParameters['migrations'] != null) {
-                formParams.append('migrations', requestParameters['migrations']);
-            }
-            let urlPath = `/api/v1/database/migrations`;
-            const response = yield this.request({
-                path: urlPath,
-                method: 'POST',
-                headers: headerParameters,
-                query: queryParameters,
-                body: formParams,
-            }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => (0, index_1.V1MigrationSuccessResponseFromJSON)(jsonValue));
-        });
-    }
-    /**
-     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-     * Upload database migrations
-     */
-    uploadDatabaseMigrations(requestParameters, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.uploadDatabaseMigrationsRaw(requestParameters, initOverrides);
-            return yield response.value();
-        });
-    }
-}
-exports.V1DatabaseApi = V1DatabaseApi;

package/dist/esm/apis/V1DatabaseApi.d.ts

@@ -1,31 +0,0 @@
-/**
- * Omnibase REST API
- * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
- *
- * The version of the OpenAPI document: 0.9.13
- * Contact: support@omnibase.dev
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-import * as runtime from '../runtime';
-import type { V1MigrationSuccessResponse } from '../models/index';
-export interface UploadDatabaseMigrationsRequest {
-    migrations: Blob;
-}
-/**
- *
- */
-export declare class V1DatabaseApi extends runtime.BaseAPI {
-    /**
-     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-     * Upload database migrations
-     */
-    uploadDatabaseMigrationsRaw(requestParameters: UploadDatabaseMigrationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V1MigrationSuccessResponse>>;
-    /**
-     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-     * Upload database migrations
-     */
-    uploadDatabaseMigrations(requestParameters: UploadDatabaseMigrationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V1MigrationSuccessResponse>;
-}

package/dist/esm/apis/V1DatabaseApi.js

@@ -1,82 +0,0 @@
-/* tslint:disable */
-/* eslint-disable */
-/**
- * Omnibase REST API
- * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
- *
- * The version of the OpenAPI document: 0.9.13
- * Contact: support@omnibase.dev
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
-    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
-    return new (P || (P = Promise))(function (resolve, reject) {
-        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
-        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
-        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
-        step((generator = generator.apply(thisArg, _arguments || [])).next());
-    });
-};
-import * as runtime from '../runtime';
-import { V1MigrationSuccessResponseFromJSON, } from '../models/index';
-/**
- *
- */
-export class V1DatabaseApi extends runtime.BaseAPI {
-    /**
-     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-     * Upload database migrations
-     */
-    uploadDatabaseMigrationsRaw(requestParameters, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters['migrations'] == null) {
-                throw new runtime.RequiredError('migrations', 'Required parameter "migrations" was null or undefined when calling uploadDatabaseMigrations().');
-            }
-            const queryParameters = {};
-            const headerParameters = {};
-            if (this.configuration && this.configuration.apiKey) {
-                headerParameters["Authorization"] = yield this.configuration.apiKey("Authorization"); // BearerAuth authentication
-            }
-            const consumes = [
-                { contentType: 'multipart/form-data' },
-            ];
-            // @ts-ignore: canConsumeForm may be unused
-            const canConsumeForm = runtime.canConsumeForm(consumes);
-            let formParams;
-            let useForm = false;
-            // use FormData to transmit files using content-type "multipart/form-data"
-            useForm = canConsumeForm;
-            if (useForm) {
-                formParams = new FormData();
-            }
-            else {
-                formParams = new URLSearchParams();
-            }
-            if (requestParameters['migrations'] != null) {
-                formParams.append('migrations', requestParameters['migrations']);
-            }
-            let urlPath = `/api/v1/database/migrations`;
-            const response = yield this.request({
-                path: urlPath,
-                method: 'POST',
-                headers: headerParameters,
-                query: queryParameters,
-                body: formParams,
-            }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => V1MigrationSuccessResponseFromJSON(jsonValue));
-        });
-    }
-    /**
-     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-     * Upload database migrations
-     */
-    uploadDatabaseMigrations(requestParameters, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.uploadDatabaseMigrationsRaw(requestParameters, initOverrides);
-            return yield response.value();
-        });
-    }
-}

package/docs/V1DatabaseApi.md

@@ -1,83 +0,0 @@
-# V1DatabaseApi
-
-All URIs are relative to *http://api.omnibase.tech*
-
-| Method | HTTP request | Description |
-|------------- | ------------- | -------------|
-| [**uploadDatabaseMigrations**](V1DatabaseApi.md#uploaddatabasemigrations) | **POST** /api/v1/database/migrations | Upload database migrations |
-
-
-
-## uploadDatabaseMigrations
-
-> V1MigrationSuccessResponse uploadDatabaseMigrations(migrations)
-
-Upload database migrations
-
-Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-
-### Example
-
-```ts
-import {
-  Configuration,
-  V1DatabaseApi,
-} from '@omnibase/core-js';
-import type { UploadDatabaseMigrationsRequest } from '@omnibase/core-js';
-
-async function example() {
-  console.log("🚀 Testing @omnibase/core-js SDK...");
-  const config = new Configuration({ 
-    // To configure API key authorization: BearerAuth
-    apiKey: "YOUR API KEY",
-  });
-  const api = new V1DatabaseApi(config);
-
-  const body = {
-    // Blob | Zip file containing SQL migration files
-    migrations: BINARY_DATA_HERE,
-  } satisfies UploadDatabaseMigrationsRequest;
-
-  try {
-    const data = await api.uploadDatabaseMigrations(body);
-    console.log(data);
-  } catch (error) {
-    console.error(error);
-  }
-}
-
-// Run the test
-example().catch(console.error);
-```
-
-### Parameters
-
-
-| Name | Type | Description  | Notes |
-|------------- | ------------- | ------------- | -------------|
-| **migrations** | `Blob` | Zip file containing SQL migration files | [Defaults to `undefined`] |
-
-### Return type
-
-[**V1MigrationSuccessResponse**](V1MigrationSuccessResponse.md)
-
-### Authorization
-
-[BearerAuth](../README.md#BearerAuth)
-
-### HTTP request headers
-
-- **Content-Type**: `multipart/form-data`
-- **Accept**: `application/json`
-
-
-### HTTP response details
-| Status code | Description | Response headers |
-|-------------|-------------|------------------|
-| **200** | Migrations applied successfully |  -  |
-| **400** | No migrations zip file provided |  -  |
-| **401** | Invalid or missing JWT token |  -  |
-| **500** | Migration execution failed |  -  |
-
-[[Back to top]](#) [[Back to API list]](../README.md#api-endpoints) [[Back to Model list]](../README.md#models) [[Back to README]](../README.md)
-

package/src/apis/V1DatabaseApi.ts

@@ -1,106 +0,0 @@
-/* tslint:disable */
-/* eslint-disable */
-/**
- * Omnibase REST API
- * Self-hostable Backend-as-a-Service providing database management, authentication, payments, storage, and email services.  ## Features - **Database**: PostgreSQL with RLS and migrations - **Authentication**: Ory Kratos integration with session management - **Payments**: Stripe integration with version-controlled billing configs - **Storage**: S3-compatible object storage with RLS - **Email**: Transactional email service - **Permissions**: Fine-grained access control via Ory Keto  ## Authentication Most endpoints require authentication via session cookies or JWT tokens. Use the appropriate security scheme based on the endpoint requirements.
- *
- * The version of the OpenAPI document: 0.9.13
- * Contact: support@omnibase.dev
- *
- * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
- * https://openapi-generator.tech
- * Do not edit the class manually.
- */
-
-
-import * as runtime from '../runtime';
-import type {
-  HandlersInternalServerErrorResponse,
-  HandlersUnauthorizedResponse,
-  V1MigrationErrorResponse,
-  V1MigrationSuccessResponse,
-} from '../models/index';
-import {
-    HandlersInternalServerErrorResponseFromJSON,
-    HandlersInternalServerErrorResponseToJSON,
-    HandlersUnauthorizedResponseFromJSON,
-    HandlersUnauthorizedResponseToJSON,
-    V1MigrationErrorResponseFromJSON,
-    V1MigrationErrorResponseToJSON,
-    V1MigrationSuccessResponseFromJSON,
-    V1MigrationSuccessResponseToJSON,
-} from '../models/index';
-
-export interface UploadDatabaseMigrationsRequest {
-    migrations: Blob;
-}
-
-/**
- * 
- */
-export class V1DatabaseApi extends runtime.BaseAPI {
-
-    /**
-     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-     * Upload database migrations
-     */
-    async uploadDatabaseMigrationsRaw(requestParameters: UploadDatabaseMigrationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<V1MigrationSuccessResponse>> {
-        if (requestParameters['migrations'] == null) {
-            throw new runtime.RequiredError(
-                'migrations',
-                'Required parameter "migrations" was null or undefined when calling uploadDatabaseMigrations().'
-            );
-        }
-
-        const queryParameters: any = {};
-
-        const headerParameters: runtime.HTTPHeaders = {};
-
-        if (this.configuration && this.configuration.apiKey) {
-            headerParameters["Authorization"] = await this.configuration.apiKey("Authorization"); // BearerAuth authentication
-        }
-
-        const consumes: runtime.Consume[] = [
-            { contentType: 'multipart/form-data' },
-        ];
-        // @ts-ignore: canConsumeForm may be unused
-        const canConsumeForm = runtime.canConsumeForm(consumes);
-
-        let formParams: { append(param: string, value: any): any };
-        let useForm = false;
-        // use FormData to transmit files using content-type "multipart/form-data"
-        useForm = canConsumeForm;
-        if (useForm) {
-            formParams = new FormData();
-        } else {
-            formParams = new URLSearchParams();
-        }
-
-        if (requestParameters['migrations'] != null) {
-            formParams.append('migrations', requestParameters['migrations'] as any);
-        }
-
-
-        let urlPath = `/api/v1/database/migrations`;
-
-        const response = await this.request({
-            path: urlPath,
-            method: 'POST',
-            headers: headerParameters,
-            query: queryParameters,
-            body: formParams,
-        }, initOverrides);
-
-        return new runtime.JSONApiResponse(response, (jsonValue) => V1MigrationSuccessResponseFromJSON(jsonValue));
-    }
-
-    /**
-     * Uploads SQL migration files and applies them to the user\'s PostgreSQL database.  ## Authentication Requires JWT token (typically used by CLI tools, not browser sessions).  ## Migration Format Upload a zip file containing SQL files named like: `001-seed.sql`, `002-rls.sql`, etc. Files are automatically renamed to golang-migrate format: `001_seed.up.sql`, `002_rls.up.sql`.  ## Use Cases - CLI migration uploads via `omnibase db migration push` - CI/CD pipeline integrations - Programmatic schema management
-     * Upload database migrations
-     */
-    async uploadDatabaseMigrations(requestParameters: UploadDatabaseMigrationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<V1MigrationSuccessResponse> {
-        const response = await this.uploadDatabaseMigrationsRaw(requestParameters, initOverrides);
-        return await response.value();
-    }
-
-}