We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, thanks for this project, it's been really helpful for us!
I noticed that conditions are not checked when you delete an object. When we create or update objects conditions work as expected.
I'm sending a request with an invalid version 123:
123
DELETE /storage/v1/b/tempo/o/overrides%2Fsingle-tenant%2Foverrides.json?alt=json&ifGenerationMatch=123&prettyPrint=false
This request should fail but it succeeds with a 200 and deletes the object.
Digging through the code it seems storageFS.DeleteObject does not pass in conditions:
storageFS.DeleteObject
fake-gcs-server/internal/backend/fs.go
Lines 379 to 391 in 4f69521
Would the solution be as simple as passing in the Conditions and checking them like you do in CreateObject?
Conditions
CreateObject
Line 199 in 4f69521
The text was updated successfully, but these errors were encountered:
@fsouza Hi, are there any updates on that?
Sorry, something went wrong.
No branches or pull requests
Hi, thanks for this project, it's been really helpful for us!
I noticed that conditions are not checked when you delete an object. When we create or update objects conditions work as expected.
I'm sending a request with an invalid version
123
:This request should fail but it succeeds with a 200 and deletes the object.
Digging through the code it seems
storageFS.DeleteObject
does not pass in conditions:fake-gcs-server/internal/backend/fs.go
Lines 379 to 391 in 4f69521
Would the solution be as simple as passing in the
Conditions
and checking them like you do inCreateObject
?fake-gcs-server/internal/backend/fs.go
Line 199 in 4f69521
The text was updated successfully, but these errors were encountered: