Member Junction
    Preparing search index...

    Input to the RSU pipeline.

    interface RSUPipelineInput {
        AdditionalSchemaInfo?: string;
        AdditionalSchemaInfoAuthoritative?: boolean;
        AffectedTables: string[];
        Description: string;
        MetadataFiles?: { Content: string; Path: string }[];
        MigrationSQL: string;
        PostRestartFiles?: { Content: string; Path: string }[];
        SkipGitCommit?: boolean;
        SkipRestart?: boolean;
    }
    Index

    Properties

    AdditionalSchemaInfo?: string

    Optional: additionalSchemaInfo JSON content for soft FKs.

    AdditionalSchemaInfoAuthoritative?: boolean

    When true, this input's AdditionalSchemaInfo payload represents the FULL current resolution for each schema it contains (e.g. a schema-evolution refresh that re-resolved the whole connector). The writer then REPLACES each contained schema's table list wholesale — pruning entries for tables that vanished from the resolution (rsuplan: "adds new ones, removes old ones that no longer exist"). Leave false/unset for subset builds (ApplyAll of selected objects), where pruning would wrongly delete other tables' soft constraints.

    AffectedTables: string[]

    Tables being created or modified (used in branch naming and logging).

    Description: string

    Descriptive name for this schema change.

    MetadataFiles?: { Content: string; Path: string }[]

    Optional: metadata JSON files for mj-sync.

    MigrationSQL: string

    The migration SQL to execute (from SchemaEngine or any other source).

    PostRestartFiles?: { Content: string; Path: string }[]

    Optional files to write to disk before restart. RSU does not read or interpret these — it simply persists them so they survive the process restart. The caller is responsible for reading them on the other side.

    SkipGitCommit?: boolean

    If true, skip the git commit/push step (Phase 2).

    SkipRestart?: boolean

    If true, skip MJAPI restart (useful for batching multiple changes).