From 3f801d1279eeb5cea50dc874be9f77ba8eb21c85 Mon Sep 17 00:00:00 2001
From: Patrick Jungermann <Patrick.Jungermann@gmail.com>
Date: Thu, 7 Apr 2022 16:21:25 +0200
Subject: [PATCH] feat: handle potential future case of no awsS3 integration

Relates-to: PR #10480
Signed-off-by: Patrick Jungermann <Patrick.Jungermann@gmail.com>
---
 .../src/providers/AwsS3EntityProvider.ts                       | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/plugins/catalog-backend-module-aws/src/providers/AwsS3EntityProvider.ts b/plugins/catalog-backend-module-aws/src/providers/AwsS3EntityProvider.ts
index f068e40130..2e64699d8b 100644
--- a/plugins/catalog-backend-module-aws/src/providers/AwsS3EntityProvider.ts
+++ b/plugins/catalog-backend-module-aws/src/providers/AwsS3EntityProvider.ts
@@ -63,6 +63,9 @@ export class AwsS3EntityProvider implements EntityProvider {
     // In this case, we still want the first one though, but have no means to select it
     // just from the bucket name (and region).
     const integration = ScmIntegrations.fromConfig(configRoot).awsS3.list()[0];
+    if (!integration) {
+      throw new Error('No integration found for awsS3');
+    }
 
     return providerConfigs.map(
       providerConfig =>