(aws-ec2): Missing enum entries for ec2.SubnetType in CDK-1.x

[anon-44]

What is the problem?

CDK-1.122.0 introduced new entries in the SubnetType enum, while marking a few old ones as deprecated - 2023004

While the documentation includes the deprecation notice and recommendations for using the new entries, the new entries aren't actually present in the enum.
Docs - https://docs.aws.amazon.com/cdk/api/v1/java/index.html?software/amazon/awscdk/services/ec2/SubnetType.html

CDK-2.x has the entries present(likely because the old entries are removed altogether), but the provided example still references the old entries from CDK-1.x. See https://docs.aws.amazon.com/cdk/api/v2/java/index.html?software/amazon/awscdk/services/ec2/SubnetType.html

Reproduction Steps

N/A

What did you expect to happen?

CDK-1.x should include the suggested new entries in the SubnetType enum along with the old deprecated entries.

What actually happened?

CDK-1.x does not include the suggested new entries in the SubnetType enum.

CDK CLI Version

cdk-1.131.0

Framework Version

No response

Node.js Version

14

OS

MacOS-11.6

Language

Java

Language Version

Java-8

Other information

No response

[peterwoodworth]

Hey @anon-44, thanks for reporting this

This is a known issue for some of our non-TypeScript libraries. The source of this issue is due to JSII and the issue is here. It's not fixed yet, but as you've found, the issue isn't present in v2.

[anon-44]

So is the recommendation here to upgrade to v2? Will this not be fixed in v1 releases?

[peterwoodworth]

There's no ETA for the fix in v1, so you should upgrade to v2 if you don't want to deal with the warnings or use any workarounds (if there are any, I don't know of any off the top of my head).

I recommend upgrading to v2 anyway, I find it a much nicer experience overall. Here's our docs on how to upgrade 🙂

[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.