-
Notifications
You must be signed in to change notification settings - Fork 552
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
rptest: Fix s3.copy_object when running on GCP #16428
Conversation
Running on GCP env
|
13788ed
to
8befeb7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/44593#018d6586-29b8-4f73-a3c2-c48abd1c49b3 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/44593#018d6586-29bc-4acb-a9b1-19a6df8a53d4 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/44593#018d6597-3bf7-4728-a97b-88ba7bbb77d1 |
/backport v23.3.x |
When running boto3 client versus AWS it uses own header to point to object that needs to be copied.
The same function is usable for GCP's storage, but with custom header.
This PR adds custom_headers handling to CopyObject function
Backport needed only to v23.3.x due to GCP runs only supported for that version
Also v23.1.x will reach end of support soon.
Fixes: #15211
Backports Required
Release Notes