This bridged provider exposes two ways of working with the S3 Bucket resource: Bucket and BucketV2. This creates confusion for which one the users should be using. Additionally, there are sidecar resources such as aws.s3.BucketLifecycleConfigurationV2 that behave incorrectly when used with the wrong lineage of Bucket.

The ideal outcome here is having:

• only one recommended way to work with s3 buckets and associated configurations
• safe migration path for all current uses of buckets and configurations

Background/history:

• BucketV2 is the projection of the resource maintained upstream
• Bucket is a Pulumi-maintained forked resource that exists to avoid pushing breaking changes on Pulumi users back at the point where upstream made breaking changes (hence BucketV2)