Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Keep original MPU object etag after restore #5683

Merged
merged 2 commits into from
Oct 3, 2024
Merged

Keep original MPU object etag after restore #5683

merged 2 commits into from
Oct 3, 2024

Commits on Oct 3, 2024

  1. keep original MPU object etag after restore 

    When restoring an MPU, the object data might be PUT with a
different number of parts, which in turn changes the etag of
the object as it is calculated based on the etag of each uploaded
part.

We now keep the same etag in case of a restore to avoid breaking the
expiration of the restored object as it checks the etag of the object
before expiting.

The new etag is kept in the metadata of the object and can be viewed
with a head-object operation when passing the "x-amz-scal-archive-info"
header.

Issue: CLDSRV-564
    @Kerkesni
    Kerkesni committed Oct 3, 2024
    Configuration menu
    Copy the full SHA
    c6b9258 View commit details
    Browse the repository at this point in the history

  2. Enforce scubaclient version 

    Keep the version from lockfile, pending a proper release.
It also seems "latest" changes cannot be integrated at the moment.

Also, need to use specific version of typescript, as scubaclient does
not (reportedly) support latest releases (5.x).

Issue: CLDSRV-562
    @francoisferrand @Kerkesni
    francoisferrand authored and Kerkesni committed Oct 3, 2024
    Configuration menu
    Copy the full SHA
    38dd70e View commit details
    Browse the repository at this point in the history