Skip to content

[Merge 2nd] Generate AbortMultipartUpload, CreateBucketMetadataTableConfiguration and DeleteBucket related operations. #3870

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 13, 2025

Conversation

peterrsongg
Copy link
Contributor

@peterrsongg peterrsongg commented Jun 10, 2025

Description

This PR generates more S3 operations, but the main addition here is the CustomizeMarshaller partial method that will be generated on every rest-xml request marshaller. 99% of services won't implement this, but for those operations that have some sort of customization, we will create a partial of the marshaller and implement this method. (Discussed with Norm).

Motivation and Context

Testing

Assembly Comparer was run and no breaking changes in non-internal namespaces
DRY_RUN-94321c15-4f1e-4c55-aef9-e9f9c8e1e476

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

  • My code follows the code style of this project
  • My change requires a change to the documentation
  • I have updated the documentation accordingly
  • I have read the README document
  • I have added tests to cover my changes
  • All new and existing tests passed

License

  • I confirm that this pull request can be released under the Apache 2 license

@peterrsongg peterrsongg force-pushed the petesong/generate-s3-phase-1-part3 branch 6 times, most recently from 6ffbc9b to ec7ff4a Compare June 13, 2025 03:19
@peterrsongg peterrsongg force-pushed the petesong/generate-s3-phase-1-part3 branch from ec7ff4a to c289d85 Compare June 13, 2025 03:57
@@ -736,12 +736,12 @@
</None>
</ItemGroup>
<ItemGroup Condition="'$(TargetFramework)' == 'netstandard2.0'">
<PackageReference Include="Microsoft.CSharp" Version="4.4.1" />
<PackageReference Include="Microsoft.CSharp" Version="4.4.1" />
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was already here

<ItemGroup Condition="'$(TargetFramework)' == 'netstandard2.0'">
<PackageReference Include="Microsoft.CSharp" Version="4.4.1" />
</ItemGroup>
<ItemGroup Condition="'$(TargetFramework)' == 'net45'">
<Reference Include="Microsoft.CSharp" />
</ItemGroup>
<ItemGroup Condition="'$(TargetFramework)' != 'net45'">
<PackageReference Include="System.CodeDom" Version="6.0.0" />
</ItemGroup>

@@ -44,11 +44,6 @@ public partial class ListBucketsResponse : AmazonWebServiceResponse
/// <para>
/// The list of buckets owned by the requester.
/// </para>
/// <para />
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this won't actually be deleted. Norm's change is in the structuregenerator.cs file. What happened is it was in the tt file but I didnt run the custom tool so when I generated it got deleted. I reran the custom tool to include norm's change so this will remain the same when we actually release.

@@ -99,12 +117,13 @@ namespace <#=this.Config.Namespace #>.Model.Internal.MarshallTransformations
ProcessEndpointHostPrefixMembers(3, "publicRequest", this.Operation);
}
#>

PostMarshallCustomization(request, publicRequest);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since 99% of services won't implement this, why not add it only for the marshallers that need it instead of affecting all the xml marshallers?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Norm and I talked and he wanted this mechanism in here instead of another customization entry which would tell us to generate this for a specific subset.

Copy link
Member

@normj normj Jun 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the other 99% won't implement the partial PostMarshallCustomization the compiler will just compile it away as if it doesn't exists. There is no runtime cost to the other marshallers and I want to avoid as much as possible in the end of this project the number of S3 specific checks we need to do in the generator.

Plus it might be a useful customization point in the future for other services.

@peterrsongg peterrsongg merged commit 0187041 into development Jun 13, 2025
1 check passed
@peterrsongg peterrsongg deleted the petesong/generate-s3-phase-1-part3 branch June 13, 2025 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants