Enumeration: ResponsibleParty
Defined in: packages/depot-cdk/src/stage-depot-migration-types.ts:117
Enumeration Members
EXECUTED_BY_SENDER
EXECUTED_BY_SENDER:
"executed_by_sender"
Defined in: packages/depot-cdk/src/stage-depot-migration-types.ts:131
Depot has already executed the migration plan synchronously. No further action necessary. This event is sent at roughly the time a MigrationLifecycleEventType.DEPLOYED event is sent.
MIGRATIONS_DISABLED
MIGRATIONS_DISABLED:
"migrations_disabled"
Defined in: packages/depot-cdk/src/stage-depot-migration-types.ts:125
Migrations are disabled for this dataset. Even if a migration plan is not empty, an operator prevented the migrations from being executed at all by the process automation. It might be possible to trigger the migration execution manually, or it may be expected that an operator will perform manually any required actions so that the database state is consistent with the logical state recorded within Depot.
TO_BE_EXECUTED_BY_RECEIVER
TO_BE_EXECUTED_BY_RECEIVER:
"to_be_executed_by_receiver"
Defined in: packages/depot-cdk/src/stage-depot-migration-types.ts:141
Depot has not or not yet executed the migration plan synchronously. The receiver is responsible for calling back the Depot asynchronous migration execution API to execute the migration plan.
Note that unless you have set the StageDepotDatasetProps.migrationOptions.customEventBinding to true, the migration plan will be executed automatically by the Depot process automation itself; it will set up an EventBridge rule reacting to this message on your behalf.