From 8829e175f2cd8334373ba6971b181631a660a050 Mon Sep 17 00:00:00 2001 From: Patrick Jungermann Date: Wed, 15 Jun 2022 13:15:52 +0200 Subject: [PATCH] fix: allow frontend visibility for `integrations` itself Currently, `integrations` is retrieved at catalog-import to check configured integrations. This could fail if there was no config below `integrations` which has `@visibility frontend`. This happened if no integration or only non-Github integrations without frontend visible properties like `integrations.bitbucketCloud` are used. After this change, at least `integrations` will always be visible to the frontend. Closes: #11700 Signed-off-by: Patrick Jungermann --- .changeset/sweet-plants-sparkle.md | 5 +++++ packages/integration/config.d.ts | 5 ++++- 2 files changed, 9 insertions(+), 1 deletion(-) create mode 100644 .changeset/sweet-plants-sparkle.md diff --git a/.changeset/sweet-plants-sparkle.md b/.changeset/sweet-plants-sparkle.md new file mode 100644 index 0000000000..69e7647849 --- /dev/null +++ b/.changeset/sweet-plants-sparkle.md @@ -0,0 +1,5 @@ +--- +'@backstage/integration': patch +--- + +Allow frontend visibility for `integrations` itself. diff --git a/packages/integration/config.d.ts b/packages/integration/config.d.ts index c14f5c76cd..22acc5cd70 100644 --- a/packages/integration/config.d.ts +++ b/packages/integration/config.d.ts @@ -15,7 +15,10 @@ */ export interface Config { - /** Configuration for integrations towards various external repository provider systems */ + /** + * Configuration for integrations towards various external repository provider systems + * @visibility frontend + */ integrations?: { /** Integration configuration for Azure */ azure?: Array<{