-
Notifications
You must be signed in to change notification settings - Fork 2
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
bugfix: S3UTILS-110 pass VersionId to PutMetadata route #265
Draft
jonathan-gramain
wants to merge
11
commits into
development/1.13
Choose a base branch
from
bugfix/S3UTILS-110-crrExistingObjectsPutMetadataVersionId
base: development/1.13
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+398
−307
Draft
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
7e32503
S3UTILS-110 revert crrExistingObjects to 1.4.1 version
jonathan-gramain 7a85156
bugfix: ZENKO-2536 crrExistingObjects: update microVersionId
jonathan-gramain 38a6bd4
bugfix: ZENKO-2555 Fix bug on updating metadata
ba45290
S3C-2662: LISTING_LIMIT configurable via env var
scality-gdoumergue 927c1ac
feature: S3UTILS-29 huge lint overhaul from upgraded eslint
miniscruff 5152f11
Update the replication status directly
francoisferrand 02f2669
Initialize replicationInfo if not present
francoisferrand fd7fa67
S3UTILS-110 remove left-over CrrExistingObjects helpers
jonathan-gramain 86351da
S3UTILS-110 lint
jonathan-gramain 4c41db0
S3UTILS-110 BackbeatClient update
jonathan-gramain a6fac04
bugfix: S3UTILS-110 pass VersionId to PutMetadata route
jonathan-gramain File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
feature: S3UTILS-29 huge lint overhaul from upgraded eslint
(cherry picked from commit 724008d)
- Loading branch information
commit 927c1acdb2a7cdd1e3397510d5f9717326cc573b
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
we should not concat if
data.DeleteMarkers
is null?e.g. keep the older code or
data.Versions.concat(data.DeleteMarkers || [])
?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.
I believe this extra check was introduced in the Zenko version to cope with the change in API (using metadataUtil listing instead of S3), it should not be necessary and 1.4.1 does not have this check, as the SDK always returns an empty array if there is no delete marker.