mirror of
https://github.com/fsouza/fake-gcs-server.git
synced 2026-04-25 13:45:52 +03:00
[GH-ISSUE #909] Support preconditions on copyTo requests #141
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#141
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?
Originally created by @roeap on GitHub (Sep 1, 2022).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/909
As I just started looking into GCS, I may completely have missed something, But after some testing and browsing the code, it seems to me precoditions are currently not supported for copy requests.
It would be great to have support for these, as we are using fake-gcs to test a solution that heavily relies on copy-if-not-exists functionality. I did see several discussions around using the memory backend, which is completely fine for us.
@fsouza commented on GitHub (Sep 1, 2022):
Hi @roeap, thanks for opening the issue and thanks for confirming that using the memory backend is OK with you.
Right now, using the memory backend is the only way to have versioning. The filesystem backend doesn't really support generations. But you're right, I'm pretty sure we'd need to add support for conditions/generations in copyTo.