Description

Some teams (internal, probably also external) are using cfn2ts to generate L1 construct libraries from a spec.

Unfortunately, cfn2ts generates dependencies on APIs that are not exported from the (now export-restricted) aws-cdk-lib package, and so any L1 that's generated that is not itself bundled into aws-cdk-lib will not work anymore.

This will hurt v2 adoption, and should be rectified by making the APIs that cfn2ts depends on public (or at least, importable as a TypeScript-only helper API, look at how CDK Pipelines did that).

(Ask @rix0rrr for internal contacts)

Use Case

Generating L1s external to CDK

Proposed Solution

Stabilizing the contract

Other information

No response

Acknowledge

• I may be able to implement this feature request
• This feature might incur a breaking change