mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-26 14:15:49 +03:00
[PR #1254] [MERGED] Disallow composing more than 32 objects at once #1331
Labels
No labels
bug
compatibility-issue
docker
documentation
enhancement
help wanted
needs information
pull-request
question
stale
unfortunate
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/fake-gcs-server#1331
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/fsouza/fake-gcs-server/pull/1254
Author: @manuteleco
Created: 7/17/2023
Status: ✅ Merged
Merged: 7/30/2023
Merged by: @fsouza
Base:
main← Head:limit_compose_to_32_objects📝 Commits (1)
b83a306Disallow composing more than 32 objects at once📊 Changes
2 files changed (+23 additions, -0 deletions)
View changed files
📝
fakestorage/object.go(+8 -0)📝
fakestorage/object_test.go(+15 -0)📄 Description
The Google Cloud Storage API does not allow it either (see documentation). Trying to compose more than 32 objects at once qualifies as a 400 BadRequest. This is the body that GCS returns in such a case:
Note that GCS supports composing more than 32 objects into one. But it requires multiple
composecalls, each one composing at most 32 objects in one go.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.