-
Notifications
You must be signed in to change notification settings - Fork 252
CLDSRV-741: Bypass PutObj max size 5GB S3C-10336 #5935
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
Conversation
Hello bourgoismickael,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
@@ Coverage Diff @@
## development/9.0 #5935 +/- ##
================================================
Coverage 83.18% 83.18%
================================================
Files 188 188
Lines 12103 12105 +2
================================================
+ Hits 10068 10070 +2
Misses 2035 2035
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
| /** | ||
| * S3C-10336: PutObject max size of 5GB is new in 9.5.1 | ||
| * Provides a way to bypass the new validation if it breaks customer workflows | ||
| */ |
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.
| /** | |
| * S3C-10336: PutObject max size of 5GB is new in 9.5.1 | |
| * Provides a way to bypass the new validation if it breaks customer workflows | |
| */ |
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.
this is documentation for the flag
We don't want to disable by default. But in case a customer has problems with this new limit in S3C, we want a way to easily disable the limit to give time to customer to migrate its applications to MPU
e5b9fae to
d8ea3d6
Compare
|
/approve |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: git fetch
git checkout -B w/9.1/improvement/CLDSRV-741-bypass-putobj5G origin/development/9.1
git merge origin/improvement/CLDSRV-741-bypass-putobj5G
# <intense conflict resolution>
git commit
git push -u origin w/9.1/improvement/CLDSRV-741-bypass-putobj5GThe following options are set: approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-741. Goodbye bourgoismickael. The following options are set: approve |
We don't want to disable by default.
But in case a customer has problems with this new limit in S3C,
we want a way to easily disable the limit to give time to customer
to migrate its applications to MPU