https://pulumi.com logo
#aws
Title
# aws
d

dry-journalist-60579

05/11/2023, 1:51 PM
Soooo… can anyone tell me why it’s
BucketV2
but
BucketObjectv2
? My eye is twitching because that
v
is little
l

little-cartoon-10569

05/11/2023, 8:47 PM
Unsarcastically: the most common reason for naming mistakes is: people.
r

red-match-15116

05/11/2023, 9:09 PM
the tl;dr is that it was a human error that is really hard to fix after the fact
d

dry-journalist-60579

05/11/2023, 10:30 PM
Heh sorry to give such a hard time
But could there be an alias?
BucketObjectV2 = BucketObjectv2
r

red-match-15116

05/11/2023, 10:32 PM
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)
d

dry-journalist-60579

05/12/2023, 11:57 AM
files?
m

mysterious-ability-48871

05/12/2023, 1:37 PM
Are there some linters which can catch these issues?
s

stocky-restaurant-98004

05/12/2023, 1:44 PM
@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.
d

dry-journalist-60579

05/12/2023, 1:47 PM
ah that’s a shame
womp womp 🙂
thank you!