spec2cdk: schemas under temporary-schema/us-east-1 is not being auto-populated into aws-cdk-lib

[GavinZZ]

Describe the bug

I'm testing adding CFN schemas to temporary-schema/us-east-1 under the spec2cdk tool, but I realize that if this is a new service, the generated L1 is now being added into the packages/aws-cdk-lib.

After some investigation, the new schema service name is not being recognized in the db object https://github.com/aws/aws-cdk/blob/main/tools/@aws-cdk/spec2cdk/lib/generate.ts#L128.

However, I did try running below directly from spec2cdk tool and the generation is working.

bin/spec2cdk lib/services --service AWS::MyServiceName

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Library Version

N/A

Expected Behavior

Generate the new service L1 successfully into packages/aws-cdk-lib

Current Behavior

Does not generate the new service L1 construct

Reproduction Steps

1. Add a new schema file to temporary-schema/us-east-1 that is a new service namespace
2. run yarn build in packages/aws-cdk-lib
3. Observe that the new L1 is not generated.

Possible Solution

No response

Additional Information/Context

No response

AWS CDK Library version (aws-cdk-lib)

latest

AWS CDK CLI version

Not relevant

Node.js Version

20

OS

N/A

Language

TypeScript

Language Version

No response

Other information

No response

[GavinZZ]

I think this line needs to const db = await loadPatchedSpec(); rather than loadAwsServiceSpec.

[GavinZZ]

I can confirm that if I changed this line the above proposed solution, I am able to see my service L1 construct generated successfully.

[pahud]

Hi @GavinZZ

I was not able to find last working release for now. But looking at current codebase.

The problem seems to be in tools/@aws-cdk/spec2cdk/lib/cfn2ts/index.ts, the generateAll() function:

export async function generateAll(...) {
  const db = await loadAwsServiceSpec();  // ← Only loads official specs
  const allScopes = getAllScopes(db, 'cloudFormationNamespace');  // ← Gets scopes from incomplete db
  // ... builds moduleMap from these scopes
  const generated = await generateModules(...);  // ← Too late, scopes already determined
}

The scopes are extracted from a database that doesn't include temporary-schemas, so new services are never added to the generation list and for some reason loadPatchedSpec() was skipped.

I might be wrong. Will bring this up to the team for review.