From 56df72812216b1af731f31b0ffa0b177048f21a9 Mon Sep 17 00:00:00 2001 From: solimant Date: Wed, 20 Sep 2023 22:33:29 -0400 Subject: [PATCH] Update external-integrations.md Signed-off-by: solimant --- .../software-catalog/external-integrations.md | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/docs/features/software-catalog/external-integrations.md b/docs/features/software-catalog/external-integrations.md index 0f2459d6e0..0286b1f580 100644 --- a/docs/features/software-catalog/external-integrations.md +++ b/docs/features/software-catalog/external-integrations.md @@ -66,10 +66,14 @@ have to supply a (unique) name, and accept a connection from the environment through which you can issue writes. The rest is up to the individual provider implementation. -It is up to you where you put the code for this new processor class. For quick +It is up to you where you put the code for this new provider class. For quick experimentation you could place it in your backend package, but we recommend -putting all extensions like this in a backend plugin package of their own in the -`plugins` folder of your Backstage repo. +putting all extensions like this in a backend module package of their own in the +`plugins` folder of your Backstage repo: + +```sh +yarn new --select backend-module --option id=catalog +``` The class will have this basic structure: @@ -495,8 +499,12 @@ subclass that can be added to this catalog builder. It is up to you where you put the code for this new processor class. For quick experimentation you could place it in your backend package, but we recommend -putting all extensions like this in a backend plugin package of their own in the -`plugins` folder of your Backstage repo. +putting all extensions like this in a backend module package of their own in the +`plugins` folder of your Backstage repo: + +```sh +yarn new --select backend-module --option id=catalog +``` The class will have this basic structure: