fix aws header list parsing #6435
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue with the ASF parser, where it didn't consider list-encoded types in header locations. See my comment in #6422, fix should be fairly self-explanatory.
I also added an integration test, but the feature is not implemented in moto yet, so cannot fix the issue right away.
List header shapes
We previously made the assumption that shapes with the location "header" are only ever primitive types. However, "ObjectAttributes" in "s3.GetObjectAttributes" is a list shape which has the location "header".
The header arrives as, e.g.,
x-amz-object-attributes: ObjectSize,StorageClass
.I briefly verified that it's the only one. Here's the list of all shape members with location "header" that are not strings: