TransitGatewayAttachment: AWS::EC2::TransitGatewayAttachment ApplianceModeSupport options are named "applianceModeSupport"

[JPLemelin]

Describe the bug

After upgrading from 2.56.0 to 2.56.1, the CloudFormation attribute "ApplianceModeSupport" was rename with a lower case

Sample of construct usage:

const transitGatewayAttachmentVpc = new ec2.CfnTransitGatewayAttachment(this, 'tgw-att-vpc', {
  transitGatewayId: transitGateway.ref,
  vpcId: vpc.vpcId,
  subnetIds: vpc.selectSubnets({subnetGroupName: 'tgw-subnet'}).subnetIds,
  options: {
    applianceModeSupport: 'enable',
  },
}

Diff after upgrading

[~] AWS::EC2::TransitGatewayAttachment tgw-att-vpc tgwattvpc 
 └─ [~] Options
     ├─ [-] Removed: .ApplianceModeSupport
     └─ [+] Added: .applianceModeSupport

Expected Behavior

Cloudformation generated should be named accourding to the doc: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-transitgatewayvpcattachment-options.html#cfn-ec2-transitgatewayvpcattachment-options-appliancemodesupport

Current Behavior

The stack failed to deploy

The stack named hub-network failed to deploy: UPDATE_ROLLBACK_COMPLETE: Properties validation failed for resource tgwattvpc with message:
#/Options: extraneous key [applianceModeSupport] is not permitted

Reproduction Steps

Just execute cdk deploy cmd

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.56.1

Framework Version

No response

Node.js Version

16

OS

MacOs

Language

Typescript

Language Version

No response

Other information

No response

[peterwoodworth]

This is the same cause as the other issues I've named in this comment. tl;dr we got stuck between a rock and a hard place regarding typing of resources cfnspec changed. Going forward we're looking how to prevent this from happening again. In the meantime, you'll need to define the properties with capital letters

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.