Closed Bug 984731 Opened 11 years ago Closed 11 years ago

Accept DELETE requests at the root service endpoint

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rfkelly, Unassigned)

References

Details

(Whiteboard: [qa+])

Attachments

(2 files)

The tokenserver cleanup script in Bug 984297 current needs to know some internal details of the syncstorage API in order to send it a "delete all data for this user" request. ISTM this would be neater if it could assume all services accept "DELETE <endpoint-url>" as such a command. Here's what it would take to make syncstorage accept such a request.
Attachment #8392673 - Flags: review?(telliott)
OS: Linux → All
Hardware: x86_64 → All
And a corresponding docs change. It's not a big deal but this seems neater to me than calling "DELETE /storage" from the tokenserver scripts.
Attachment #8392674 - Flags: review?(telliott)
Blocks: 984297
Comment on attachment 8392674 [details] [diff] [review] sync15-docs-delete-at-endpoint-url.diff Makes sense. You delete all the stuff under /info as well. It's a little odd that you can DELETE the root, but not do anything else to it, but that's mostly aesthetic.
Attachment #8392674 - Flags: review?(telliott) → review+
Comment on attachment 8392673 [details] [diff] [review] sync15-delete-at-endpoint-url.diff Review of attachment 8392673 [details] [diff] [review]: ----------------------------------------------------------------- ::: syncstorage/views/__init__.py @@ +177,5 @@ > + storage = request.validated["storage"] > + storage.delete_storage(request.validated["userid"]) > + return {} > + > + Are we going to remove the corresponding DELETE /storage? The test implies we should, but there's no removal here.
Comment on attachment 8392673 [details] [diff] [review] sync15-delete-at-endpoint-url.diff Review of attachment 8392673 [details] [diff] [review]: ----------------------------------------------------------------- I guess we probably shouldn't for now, come to think of it, since the client will still be deleting to the other endpoint. Adding Nick and Richard to note it as something we should deprecate.
Attachment #8392673 - Flags: review?(telliott) → review+
I think there's a difference between "delete my account" and "wipe my storage", so I see no reason to merge the two.
From the perspective of the storage server, the calls are identical, though.
Whiteboard: [qa+]
> Are we going to remove the corresponding DELETE /storage? > The test implies we should, but there's no removal here. Nope, we keep it for b/w compat, and there are other tests (unchanged by this patch) that still exercise it. https://github.com/mozilla-services/docs/commit/3a6745b332d7739905ca85c4d4852a2f3529510a https://github.com/mozilla-services/server-syncstorage/commit/986ae66ddb394c3c2097eec7580d4692b8efe92a
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
See also https://github.com/mozilla-services/server-syncstorage/issues/16 To be verified together with next deploy to Sync Stage.
I think we are all good here. Super clean Sync load tests last week and this week.
Status: RESOLVED → VERIFIED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: