[GH-ISSUE #804] Creating a bucket that already exists should return a 409 #130

Closed
opened 2026-03-03 12:08:34 +03:00 by kerem · 0 comments
Owner

Originally created by @dnerdy on GitHub (Jun 2, 2022).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/804

Both the fs and memory backend return 200 responses when creating a bucket that already exists (the fs backend uses os.MkdirAll and the memory backend allows re-creation of existing buckets as long as VersioningEnabled matches).

GCS returns a 409 response when attempting to create a bucket that already exists. It would be nice if fake-gcs-server matched this behavior.

Originally created by @dnerdy on GitHub (Jun 2, 2022). Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/804 Both the fs and memory backend return 200 responses when creating a bucket that already exists (the fs backend uses os.MkdirAll and the memory backend allows re-creation of existing buckets as long as VersioningEnabled matches). GCS returns a 409 response when attempting to create a bucket that already exists. It would be nice if fake-gcs-server matched this behavior.
kerem closed this issue 2026-03-03 12:08:34 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/fake-gcs-server#130
No description provided.