Upcoming deprecation of Aws::S3::Bucket and Aws::S3::Object?

[grncdr]

Bringing this out of a closed PR thread, which is the only place I found this deprecation discussed: #3281 (comment)

@fschwahn: just curious if the deprecation of Aws::S3::Object#upload_file is really necessary? I assume there's a lot of code relying on this, and rewriting all of that will take a lot of time. Couldn't Aws::S3::Object#upload_file use the new API under the hood?

@jterapin: Unfortunately, AWS services have discontinued their maintenance over resource models (such as S3 and EC2). The Ruby SDK uses these models to generate classes like Aws::S3::Object and Aws::S3::Bucket. As a result, we will be phasing out support for these resource classes in the upcoming MV of the Ruby SDK. Deprecation warnings are introduced to prepare for this transition ahead of time.

Am I reading that correctly that the plan is to deprecate and remove the entire Aws::S3::Bucket and Aws::S3::Object classes? That's pretty fundamental to our (and I suspect many peoples) usage of the library.

[jterapin]

Hi @grncdr! Thanks for opening this discussion. That's a valid concern and it's definitely on our mind. As of this major version (V3), we have no plans to remove the resource model.

In an upcoming major version, we're working to make sure most of the features the S3 resource models provide are available at GA. We're still thinking through how migration should happen and what the user experience should be. One idea we're considering is a compatibility shim: existing codebases could opt in to keep using the resource model without breaking, while new applications get a smaller artifact size by default.

Nothing here is finalized, it's a proposal at this point, so we'd genuinely like to hear how that approach sounds to you and others following this thread.