feat: storing executionArn in the migrations history table

RafalWilinski · Aug 10, 2022 · 4c6b75a · 4c6b75a
1 parent c4da6f6
commit 4c6b75a
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 0 deletions.
diff --git a/src/custom-resource-migrations-runner.ts b/src/custom-resource-migrations-runner.ts
@@ -80,6 +80,7 @@ export default class CustomResourceMigrationsRunner extends Construct {
                 id: migration.migrationId,
                 status: "in_progress" as MigrationStatus,
                 startedAt: response.startDate?.toISOString()!,
+                executionArn: response.executionArn!,
               }),
             });
           }

diff --git a/src/migration.ts b/src/migration.ts
@@ -75,6 +75,7 @@ export class Migration<T extends object> extends NestedStack {
           const result: ScanOutput<any, any, any> = await $AWS.DynamoDB.Scan({
             Table: table,
             ...options,
+            // Ensure ExclusiveStartKey is not overwritten by options
             ExclusiveStartKey: lastEvaluatedKey,
           });
 
@@ -137,6 +138,7 @@ export class Migration<T extends object> extends NestedStack {
               Table: table,
               TotalSegments: totalSegments,
               ...options,
+              // Ensure Segment and ExclusiveStartKey are not overwritten by options
               Segment: index,
               ExclusiveStartKey: lastEvaluatedKey,
             });

diff --git a/src/migrations-manager.ts b/src/migrations-manager.ts
@@ -25,6 +25,7 @@ export type MigrationHistoryItem = {
   id: string;
   status: MigrationStatus;
   startedAt: string;
+  executionArn: string;
   endedAt?: string;
 };