Set 'null' as version id when replicating non versioned objects

[Kerkesni]

Non versioned object are also considered a null version when in a versioned bucket, we should specify 'null' as query version id for Cloudserver to properly replicate these objects

Issue: BB-403

[bert-e]

Hello kerkesni,

My role is to assist you with the merge of this pull request. Please type @bert-e help to get information on this process, or consult the user documentation.

Status report is not available.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[Kerkesni]

/approve

[bert-e]

In the queue

The changeset has received all authorizations and has been added to the relevant queue(s). The queue(s) will be merged in the target development branch(es) as soon as builds have passed.

The changeset will be merged in:

• :heavy_check_mark: development/8.6

The following branches will NOT be impacted:

• development/7.10
• development/7.4
• development/7.70
• development/8.4
• development/8.5

There is no action required on your side. You will be notified here once the changeset has been merged. In the unlikely event that the changeset fails permanently on the queue, a member of the admin team will contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

• Any commit you add on the source branch will trigger a new cycle after the current queue is merged.
• Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a member of the admin team now.

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request into targetted development branches:

• :heavy_check_mark: development/8.6

The following branches have NOT changed:

• development/7.10
• development/7.4
• development/7.70
• development/8.4
• development/8.5

Please check the status of the associated issue BB-403.

Goodbye kerkesni.

[nicolas2bert]

Just to clarify, there seems to be 2 different cases:

Lifecycle Bucket Processor: In this case, the entry MD is sourced from either the listObject or listObjectVersions, and thus the "null" version is already appropriately set.

All the other processes: Here, we receive the pure object MD, and if the version id is undefined, a "null" version id is used for both getMetadata and putMetadata operations. CloudServer.putMetadata() will then determine how to handle the null version without a version id.

It would be interesting to consolidate/abstract the logic, so that when we utilize a versionId, we don't need to consider whether it has already been "processed" or not.

This task can be addressed in a subsequent ticket.