-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
How to create copy of object version into another bucket #403
Comments
I have found the solution. Searching for similar problems I have found issue boto/botocore#509 I have found undocumented method to specify version id in Testing it on To name specific object version as SourceObject, one has to use following pattern: Now I am able to copy from specific version using boto3. I still consider this an issue, as current version of documentation does not explain it well (it omits the version and does not explain the need to use the leading slash). Existing specification for Object.copy_from reads for the
I would propose to modify the text to clarify:
|
Thanks very much for finding the solution and sharing it! We will definitely take a look into this and see how we can improve the documentation. |
@rayluo Looking forward to that. If your updated doc explains this, it would be great. Otherwise we shall create separate issue for this particular corner case. |
With the release of boto3 1.4.0, we introduced a managed |
@vlcinsky the above problem is because of escape char , please see aws/aws-sdk-ruby#969 and draw parallel |
I have versioned bucket and need to copy set of object versions into another (non versioned) bucket.
There are some
SomeResource.copy_from
andClient.copy_object
methods.However, I was unable to find how to specify source object version_id. The only place, where I have found
CopySourceVersionId
was response, but no place to put it into request.Is there any way to copy object version into another bucket without downloading it?
With boto it was possible (but I my source bucket is having dots in names and this is not working with old
boto
any more.The text was updated successfully, but these errors were encountered: