UNPKG

@fntio/infra-client

Version:

Self-hosted AWS access portal: credential vending, target-account trust, and grant-driven private networking as CDK stacks and constructs.

32 lines (31 loc) • 1.82 kB
import * as cdk from "aws-cdk-lib"; import * as apigw from "aws-cdk-lib/aws-apigateway"; import * as dynamodb from "aws-cdk-lib/aws-dynamodb"; import * as s3 from "aws-cdk-lib/aws-s3"; import { Construct } from "constructs"; import { ResolvedPlugin } from "./registration"; import { AuditLogTarget } from "../audit-log"; export interface PluginCatalogActivationProps { readonly plugins: readonly ResolvedPlugin[]; /** The plugin-assets bucket (DataStack); uploads land under `<id>/<version>-<hash>/`, never pruned. */ readonly assetsBucket: s3.IBucket; readonly pluginCatalogTable: dynamodb.ITable; readonly accessTable: dynamodb.ITable; readonly accountsTable: dynamodb.ITable; readonly revocationsTable: dynamodb.ITable; /** Where the provider records catalog activations and tombstones; absent = log lines only. */ readonly auditLog?: AuditLogTarget; /** The core API stage and each plugin's methods: a record is written after the routes exist and, on * removal, tombstoned BEFORE they go (CloudFormation deletes dependents first). */ readonly apiStage: apigw.IStage; readonly methodsByPlugin: ReadonlyMap<string, readonly apigw.Method[]>; /** Who owns the records (the CloudFormation stack id — stable across renames of constructs); a second * deployment claiming a plugin id is a deploy error. */ readonly owner: string; } /** Uploads each plugin's UI and writes its catalog record (Custom::PluginCatalogRecord) after the asset upload, * the API stage and the plugin's methods. Delete tombstones the record; the provider raises loss notices. */ export declare class PluginCatalogActivation extends Construct { readonly records: cdk.CustomResource[]; constructor(scope: Construct, id: string, props: PluginCatalogActivationProps); }