feat: allow defining custom build log transport for techdocs

should enable way to overcome #24583 memory leak, maybe.

Signed-off-by: Heikki Hellgren <heikki.hellgren@op.fi>

plugins/techdocs-node/api-report.md

@@ -16,6 +16,7 @@ import { Logger } from 'winston';
 import { PluginEndpointDiscovery } from '@backstage/backend-common';
 import { ScmIntegrationRegistry } from '@backstage/integration';
 import { UrlReader } from '@backstage/backend-common';
+import * as winston from 'winston';
 import { Writable } from 'stream';
 
 // @public
@@ -240,6 +241,8 @@ export type SupportedGeneratorKey = 'techdocs' | string;
 
 // @public
 export interface TechdocsBuildsExtensionPoint {
+  // (undocumented)
+  setBuildLogTransport(transport: winston.transport): void;
   // (undocumented)
   setBuildStrategy(buildStrategy: DocsBuildStrategy): void;
 }

plugins/techdocs-node/src/extensions.ts

@@ -16,6 +16,7 @@
 import { createExtensionPoint } from '@backstage/backend-plugin-api';
 import { DocsBuildStrategy } from './techdocsTypes';
 import { PreparerBase, RemoteProtocol, TechdocsGenerator } from './stages';
+import * as winston from 'winston';
 
 /**
  * Extension point type for configuring Techdocs builds.
@@ -24,6 +25,7 @@ import { PreparerBase, RemoteProtocol, TechdocsGenerator } from './stages';
  */
 export interface TechdocsBuildsExtensionPoint {
   setBuildStrategy(buildStrategy: DocsBuildStrategy): void;
+  setBuildLogTransport(transport: winston.transport): void;
 }
 
 /**