-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
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
Build system: ETP lists dependency is on Amazon S3 #6792
Comments
@garvankeeley I still need information on what lists you all were generating so I can make sure those files are available in S3 |
These files are specified here: |
Dependency management questions: With what URL? And, where is the URL updated?
iOS requires a specific format that we maintain so full removal is not possible; IIUC the inputs to this processing step are changing; please describe these inputs and from that we can determine if the outputs are still supported.
Those bugs are input changes to the iOS processing script, I would imagine any input changes involving files being added or removed will result in these types of changes. Can you explain? |
➤ Laurie Marceau commented: Closing this since this won’t be fetched from an S3 bucket. |
Why/User Benefit/User Problem
Currently Firefox iOS is generating their own tracking protection lists by grabbing the raw source from shavar-prod-lists and following a similar configuration as shavar-list-creation. However, the logic to generate the tracking protection lists can fall behind (see #5559 and #5968). I suggest that Firefox iOS gets the lists from Shavar services maintained S3 files. With this transition Firefox iOS can deprecate the script to generate their own tracking protection lists and only have to maintain the script to convert the tracking protection JSON files to iOS consumable files all the while always being guaranteed to get the latest tracking protection lists from Shavar.
Acceptance Criteria (how do I know when I’m done?)
Not included
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: