Soooo… can anyone tell me why it’s

BucketV2

but

BucketObjectv2

? My eye is twitching because that

v

is little

Unsarcastically: the most common reason for naming mistakes is: people.

heh https://github.com/pulumi/pulumi-aws/issues/2157

Heh sorry to give such a hard time

I think the problem is rooted in case sensitivity issues across platforms. For what you're suggesting, both files need to exist

BucketObjectV2

and

BucketObjectv2

and that just doesn't work on some platforms. (We had the same conversation internally and concluded that this is something we'd only be able to fix on a major version change because both of those files cannot simultaneously exist)

files?

Are there some linters which can catch these issues?

@dry-journalist-60579 Each resource goes in its own file in the various SDKs. Windows is case-insensitive, so: 1. We can't alias the resource because that won't work on Windows (can't have 2 files whose names only vary by casing). 2. We can't change the name of the resource, because that's a breaking change in a very widely used resource in our most widely used provider.

ah that’s a shame