From 093388c403c0fe9725b0c2f3bc6b28aed3a4089a Mon Sep 17 00:00:00 2001 From: Laurin Quast Date: Tue, 24 Jan 2023 10:44:43 +0100 Subject: [PATCH] fix: use correct key prefix for migration (#1114) --- .../2023.01.17T10.46.28.import-legacy-s3-keys-to-database.mts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/migrations/src/actions/2023.01.17T10.46.28.import-legacy-s3-keys-to-database.mts b/packages/migrations/src/actions/2023.01.17T10.46.28.import-legacy-s3-keys-to-database.mts index 761e74a90..f85b8f0dd 100644 --- a/packages/migrations/src/actions/2023.01.17T10.46.28.import-legacy-s3-keys-to-database.mts +++ b/packages/migrations/src/actions/2023.01.17T10.46.28.import-legacy-s3-keys-to-database.mts @@ -100,7 +100,7 @@ export const up: slonik.Migration = async ({ context: { connection, sql } }) => let lastCursor: null | Cursor = null; async function seedLegacyCDNKey(item: zod.TypeOf[number]): Promise { - const s3Key = `s3-legacy-keys/${item.id}`; + const s3Key = `cdn-legacy-keys/${item.id}`; const privateAccessKey = generateLegacyCDNAccessToken(item.id); const firstCharacters = privateAccessKey.substring(0, 3); const lastCharacters = privateAccessKey.substring(privateAccessKey.length - 3);