Open Bug 2011859 Opened 1 month ago Updated 14 days ago

Remove usage of /records endpoint

Categories

(Application Services :: Remote Settings, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: leplatrem, Assigned: acottner)

References

Details

(Whiteboard: [remote-settings])

Attachments

(2 files)

5 years ago, we introduced the /changeset endpoint on Remote Settings, which unlike the /records endpoint, allows to fetch both metadata (signature) and records in one request.

In a near future, we will introduce a v2 API that will only support /changeset, which BTW will be forward compatible for clients implementing our current official specifications.

The Remote Settings client in Application Services still relies on the /records endpoint.
This ticket will track the work that will consist in replacing the endpoint.
The change is trivial since the changes field of the /changeset endpoint is the equivalent of the data field of the /records endpoint.

Note: The /changeset endpoint does not support server side filtering, but usage of get_records_with_options() were removed a few years ago (can't find related bug)

Whiteboard: [remote-settings]

I think the simplest path would be to patch this code to use changeset. It seems to be called in several android implementations already.

Attached file GitHub Pull Request
Assignee: nobody → acottner
Attachment #9546220 - Attachment description: WIP: Bug 2011859 - Preparing for application-services breaking change. Renaming RemoteSettingsConfig2 to RemoteSettingsConfig. → Bug 2011859 - Preparing for application-services breaking change. Renaming RemoteSettingsConfig2 to RemoteSettingsConfig.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: