BucketObjectv2 does not follow naming convention

[komalali]

What happened?

All other V2 resource types are suffixed with the capitalized V2 except BucketObjectv2 where v2 is not capitalized.

Couldn't find an issue where this is already captured but please close this out for a dupe if it is.

Steps to reproduce

See docs at: https://www.pulumi.com/registry/packages/aws/api-docs/s3/bucketobjectv2/

Expected Behavior

I expected it to be named BucketObjectV2

Actual Behavior

It's named BucketObjectv2

Output of pulumi about

No response

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[viveklak]

Thanks for opening the issue. @stack72 thoughts on fixing the token here and adding an alias to avoid breaks?