exportadapters

Overview ¶

Package exportadapters adapts the platform's portal stores to the export interfaces consumed by the trino and api-gateway toolkits.

The trino_export and api_export tools each declare a minimal interface subset of the portal store they need (to avoid a portal→registry→toolkit import cycle). An Exporter bridges concrete portal.AssetStore / portal.VersionStore / portal.ShareStore to those toolkit-side interfaces, translating between the toolkit's export DTOs and the portal row types.

One exporter per toolkit implements all three interfaces (asset store, version store, share creator), so wiring is a single construction whose result is assigned to each ExportDeps field. Each exporter takes its dependencies as constructor parameters (issue #756).

TrinoExporter and APIExporter are near-identical: the two toolkits define field-identical-but-distinct ExportAsset/ExportVersion DTOs in separate packages (to avoid the import cycle), and Go cannot map fields across unrelated struct types generically. The mapping is therefore written once per toolkit; token generation, the default notice, and the public-share flow are shared via portal primitives and createPublicShare.