-
Notifications
You must be signed in to change notification settings - Fork 20
impr(ARSN-529): Add RateLimitConfiguration to BucketInfo #2568
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
impr(ARSN-529): Add RateLimitConfiguration to BucketInfo #2568
Conversation
Hello tmacro,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## development/8.2 #2568 +/- ##
===================================================
+ Coverage 71.40% 71.41% +0.01%
===================================================
Files 221 222 +1
Lines 17816 17851 +35
Branches 3681 3689 +8
===================================================
+ Hits 12721 12749 +28
- Misses 5091 5098 +7
Partials 4 4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
are we sure about the target branch 8.3 is not released yet with stable aws sdk upgrade, we might not be able to test. |
I am okay, we have a feature branch in cloudserver, which we can test on. |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
|
/create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
lib/s3routes/routes/routePUT.ts
Outdated
| 200, log); | ||
| }); | ||
| } else if (query['rate-limit'] !== undefined) { | ||
| api.callApiMethod('bucketGetRateLimit', request, response, |
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.
Shouldn't this be bucketPutRateLimit
lib/s3routes/routes/routeDELETE.ts
Outdated
| } else if (query?.quota !== undefined) { | ||
| return call('bucketDeleteQuota'); | ||
| } else if (query?.['rate-limit'] !== undefined) { | ||
| return call('bucketDeleteQuota'); |
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.
for this one, bucketDeleteRateLimit?
lib/errors/arsenalErrors.ts
Outdated
|
|
||
| export const NoSuchRateLimitConfig: ErrorFormat = { | ||
| code: 404, | ||
| description: 'The specified bucket does not have a rate limit configuration.', |
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 one is more compact, what do you think?
(also looking at other configuration messages
The bucket rate limit configuration does not exist.
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.
or
The bucket rate limit configuration was not found
like:
The object lock configuration was not found'
The replication configuration was not found
f5bb404 to
fd1d771
Compare
History mismatchMerge commit #ee3ed13eb0e998dd3600a08926147e2b508132a9 on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: create_integration_branches |
|
/reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
fd1d771 to
4ba5165
Compare
History mismatchMerge commit #fd1d771a3f7478085217ba13a60e69d8e38a9a6a on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: create_integration_branches |
|
/reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
4ba5165 to
7de5056
Compare
History mismatchMerge commit #4ba516583e71bf98622d1ec4f7198522771fcbc8 on the integration branch It is likely due to a rebase of the branch Please use the The following options are set: create_integration_branches |
|
/reset |
Reset completeI have successfully deleted this pull request's integration branches. The following options are set: create_integration_branches |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
|
/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 ARSN-529. Goodbye tmacro. The following options are set: approve, create_integration_branches |
No description provided.