Skip to content

Commit

Permalink
Merge branch 'improvement/ZENKO-4941' into tmp/octopus/w/2.7/improvem…
Browse files Browse the repository at this point in the history
…ent/ZENKO-4941
  • Loading branch information
bert-e committed Nov 28, 2024
2 parents 8b4f3d4 + 70d130c commit 240b4ba
Show file tree
Hide file tree
Showing 2 changed files with 44 additions and 4 deletions.
8 changes: 4 additions & 4 deletions solution/deps.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -13,10 +13,10 @@ busybox:
tag: 1.36.1
envsubst: BUSYBOX_TAG
cloudserver:
sourceRegistry: ghcr.io/scality
sourceRegistry: ghcr.io/scality/playground/wlardier
dashboard: cloudserver/cloudserver-dashboards
image: cloudserver
tag: 8.8.36
tag: 8.8.1061
envsubst: CLOUDSERVER_TAG
drctl:
sourceRegistry: ghcr.io/scality
Expand Down Expand Up @@ -103,10 +103,10 @@ s3utils:
tag: 1.14.14
envsubst: S3UTILS_TAG
scuba:
sourceRegistry: ghcr.io/scality
sourceRegistry: ghcr.io/scality/playground/wlardier
dashboard: scuba/scuba-dashboards
image: scuba
tag: 1.0.8
tag: 1.0.54
envsubst: SCUBA_TAG
sorbet:
sourceRegistry: ghcr.io/scality
Expand Down
40 changes: 40 additions & 0 deletions tests/ctst/features/quotas/Quotas.feature
Original file line number Diff line number Diff line change
Expand Up @@ -96,3 +96,43 @@ Feature: Quota Management for APIs
| 100 | 200 | 0 | IAM_USER |
| 100 | 0 | 200 | IAM_USER |
| 100 | 200 | 200 | IAM_USER |

@2.6.0
@PreMerge
@Quotas
@CronJob
@DataDeletion
@NonVersioned
Scenario Outline: Quotas are affected by deletion operations between count items runs
Given an action "DeleteObject"
And a permission to perform the "PutObject" action
And a STORAGE_MANAGER type
And a bucket quota set to 10000 B
And an account quota set to 10000 B
And an upload size of 1000 B for the object "obj-1"
And a bucket quota set to <bucketQuota> B
And an account quota set to <accountQuota> B
And a <userType> type
And an environment setup for the API
And an "existing" IAM Policy that "applies" with "ALLOW" effect for the current API
When I wait 3 seconds
And I PUT an object with size <uploadSize>
Then the API should "fail" with "QuotaExceeded"
When the "count-items" cronjobs completes without error
When I wait 3 seconds
# At this point if negative inflights are not supported, write should
# not be possible, as the previous inflights are now part of the current
# metrics.
And i delete object "obj-1"
And I wait 3 seconds
And I PUT an object with size <uploadSize>
Then the API should "succeed" with ""

Examples:
| uploadSize | bucketQuota | accountQuota | userType |
| 100 | 200 | 0 | ACCOUNT |
| 100 | 0 | 200 | ACCOUNT |
| 100 | 200 | 200 | ACCOUNT |
| 100 | 200 | 0 | IAM_USER |
| 100 | 0 | 200 | IAM_USER |
| 100 | 200 | 200 | IAM_USER |

0 comments on commit 240b4ba

Please sign in to comment.