Skip to content

Conversation

@bennettbuchanan
Copy link

@bennettbuchanan bennettbuchanan commented Mar 20, 2018

When putting an MPU object using an AWS location constraint, any user metadata is included twice.

Example response from a headObject request:

{
    "AcceptRanges": "bytes",
    "ContentType": "application/octet-stream",
    "LastModified": "Tue, 20 Mar 2018 22:11:39 GMT",
    "ContentLength": 10485762,
    "VersionId": "rbu8wlrAt7Jd_HUV9VctoSp3mIjQtg4M",
    "ETag": "\"794898c411e565027c2c3ba534b00e2d-2\"",
    "Metadata": {
        "x-amz-meta-customkey": "customValue",
        "customkey": "customValue"
    }
}

@bennettbuchanan
Copy link
Author

@ironman-machine try

@ironman-machine
Copy link
Contributor

Hello @bennettbuchanan

"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/20568' with the following env. args:

{
    "DEFAULT_BRANCH": "rel/7.2",
    "SCALITY_INTEGRATION_BRANCH": "ultron/rel/7.2",
    "REPO_NAME": "S3",
    "SCALITY_S3_BRANCH": "fix/do-not-include-untrimmed-headers-for-MPU-to-aws"
}

@bennettbuchanan
Copy link
Author

@ironman-machine
RUN_BACKBEAT_CRR_TESTS=True
try

@ironman-machine
Copy link
Contributor

Hello @bennettbuchanan

"RUN_BACKBEAT_CRR_TESTS=True": Success
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/20574' with the following env. args:

{
    "DEFAULT_BRANCH": "rel/7.2",
    "SCALITY_INTEGRATION_BRANCH": "ultron/rel/7.2",
    "REPO_NAME": "S3",
    "SCALITY_S3_BRANCH": "fix/do-not-include-untrimmed-headers-for-MPU-to-aws",
    "RUN_BACKBEAT_CRR_TESTS": "True"
}

@ironman-machine
Copy link
Contributor

PR has been updated. Reviewers, please be cautious.

@ironman-machine
Copy link
Contributor

CONFLICT (add/add): Merge conflict in lib/routes/routeBackbeat.js
CONFLICT (add/add): Merge conflict in lib/data/external/AwsClient.js

@ironman-machine
Copy link
Contributor

☀️ 👍 circleCI test succeeded!

@ironman-machine
Copy link
Contributor

PR has been updated. Reviewers, please be cautious.

@bennettbuchanan bennettbuchanan force-pushed the fix/do-not-include-untrimmed-headers-for-MPU-to-aws branch from ce1176c to 1e3d9d7 Compare April 24, 2018 17:16
@ironman-machine
Copy link
Contributor

PR has been updated. Reviewers, please be cautious.

@bennettbuchanan bennettbuchanan changed the base branch from rel/7.2 to z/1.0 April 24, 2018 17:21
dora-korpar
dora-korpar previously approved these changes Apr 24, 2018
philipyoo
philipyoo previously approved these changes Apr 24, 2018
@bennettbuchanan bennettbuchanan force-pushed the fix/do-not-include-untrimmed-headers-for-MPU-to-aws branch from 1e3d9d7 to da97719 Compare April 24, 2018 18:49
@ironman-machine ironman-machine dismissed stale reviews from dora-korpar and philipyoo April 24, 2018 18:49

Do it again human slave!:point_right: :runner: (Oh and the pull request has been updated, by the way.)

@ironman-machine
Copy link
Contributor

PR has been updated. Reviewers, please be cautious.

@bennettbuchanan bennettbuchanan force-pushed the fix/do-not-include-untrimmed-headers-for-MPU-to-aws branch from da97719 to d02dbeb Compare April 25, 2018 17:22
@ironman-machine
Copy link
Contributor

PR has been updated. Reviewers, please be cautious.

@nicolas2bert nicolas2bert merged commit d759593 into z/1.0 Apr 25, 2018
@bennettbuchanan bennettbuchanan deleted the fix/do-not-include-untrimmed-headers-for-MPU-to-aws branch December 12, 2018 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants