Signed-off-by: Fredrik Adelöw <freben@gmail.com>
2.5 KiB
@backstage/plugin-catalog-backend
| @backstage/plugin-catalog-backend |
|---|
| minor |
BREAKING: Removed all remnants of the old catalog engine implementation.
The old implementation has been deprecated for over half a year. To ensure that
you are not using the old implementation, check that your
packages/backend/src/plugins/catalog.ts creates the catalog builder using
CatalogBuilder.create. If you instead call new CatalogBuilder, you are on
the old implementation and will experience breakage if you upgrade to this
version. If you are still on the old version, see the relevant change log
entry
for migration instructions.
The minimal packages/backend/src/plugins/catalog.ts file is now:
export default async function createPlugin(
env: PluginEnvironment,
): Promise<Router> {
const builder = await CatalogBuilder.create(env);
builder.addProcessor(new ScaffolderEntitiesProcessor());
const { processingEngine, router } = await builder.build();
await processingEngine.start();
return router;
}
The following classes and interfaces have been removed:
- The
CatalogBuilderconstructor (see above; useCatalogBuilder.createinstead) AddLocationResultCommonDatabaseCreateDatabaseOptionscreateNextRouter(usecreateRouterinstead - or preferably, use therouterfield returned for you bycatalogBuilder.build())DatabaseDatabaseEntitiesCatalog(useEntitiesCataloginstead)DatabaseLocationsCatalog(useLocationServiceinstead)DatabaseLocationUpdateLogEventDatabaseLocationUpdateLogStatusDatabaseManagerDbEntitiesRequestDbEntitiesResponseDbEntityRequestDbEntityResponseDbLocationsRowDbLocationsRowWithStatusDbPageInfoEntitiesCatalog.batchAddOrUpdateEntities(was only used by the legacy engine)EntityUpsertRequestEntityUpsertResponseHigherOrderOperationHigherOrderOperationsLocationReaderLocationReadersLocationResponseLocationsCatalogLocationUpdateLogEventLocationUpdateStatusNextCatalogBuilder(useCatalogBuilder.createinstead)NextRouterOptions(useRouterOptionsinstead)ReadLocationEntityReadLocationErrorReadLocationResultTransaction
The RouterOptions interface has been un-deprecated, and has instead found use
for passing into createRouter. Its shape has been significantly changed to
accommodate the new router.