I'm using gcs bucket for wordpress (wp-stateless plugin) after create and upload media file to a bucket. I copy it to other bucket (duplicate). But generation number of each object has been change (maybe random).

My question is: How to keep generation number same bucket source like in destination bucket?

Thanks in advance.

CodePudding user response：

Basically, there’s not an official way of keeping the same version and generation numbers when copying files from one bucket to another. This is WAI and intuitive because the version number refers to this object (which resides on this bucket), when you copy it to another bucket, it's not the same object (it's a copy) so it cannot keep the same version number.

I could think of a workaround, keeping somewhere your own version of the objects and then through the API make an organized copy. This would mean you would be dumping the bucket but you would need to have a list of all the objects and its versions and then add them in sequential order (sounds like a lot of work). You could keep your own versioning (or the same versioning) in the metadata of each object.

I would recommend that if your application depends on the object’s versioning, to use custom metadata. Basically, if you did your own versioning using custom metadata, when copying the objects to a new bucket, it would keep the same metadata.

There is already a feature request created about this. But, it has mentioned that it's currently infeasible.

However, you can raise a new feature request here