This is an automated email from the ASF dual-hosted git repository.
amoghj pushed a change to branch wip-s3sign-body
in repository https://gitbox.apache.org/repos/asf/iceberg.git
omit 56415ce24e AWS: Update S3 signer spec to allow an optional string body
in S3SignRequest. Update S3 signer parser implementation to enable
serialization/deserialization of the body. Note: This will only be populated
for requests which do not transmit relevant data to sign as part of the URI
itself (e.g. DeleteObjectsRequest)
add e03cc7f919 AWS: Update S3 signer spec to allow an optional string body
in S3SignRequest.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (56415ce24e)
\
N -- N -- N refs/heads/wip-s3sign-body (e03cc7f919)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
aws/src/main/resources/s3-signer-open-api.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
