Bug 1713606 - Add a new home for "static" Remote Settings dumps that don't need to be kept in sync with remote. r=leplatrem

Differential Revision: https://phabricator.services.mozilla.com/D116713

services/settings/dumps/main/moz.build

@@ -4,8 +4,6 @@
 
 FINAL_TARGET_FILES.defaults.settings.main += [
     "anti-tracking-url-decoration.json",
-    "doh-config.json",
-    "doh-providers.json",
     "example.json",
     "hijack-blocklists.json",
     "language-dictionaries.json",

services/settings/dumps/readme.md

@@ -4,4 +4,9 @@ In order to reduce the amount of data to be downloaded on first synchronization,
 a JSON dump from the records present on the remote server can be shipped with the
 release.
 
-A bot will update the files automatically.
+A bot will update the files automatically. For collections that should not be kept
+in sync, put the JSON dumps in ../static-dumps/ instead.
+
+Dumps from dumps/ and static-dumps/ are packaged into the same resource path,
+thus looking the same to the client code and also implying that filenames must
+be unique between the two directories.

services/settings/moz.build

@@ -7,6 +7,7 @@ with Files("**"):
 
 DIRS += [
     "dumps",
+    "static-dumps",
 ]
 
 EXTRA_COMPONENTS += [

services/settings/static-dumps/main/moz.build

@@ -0,0 +1,11 @@
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+FINAL_TARGET_FILES.defaults.settings.main += [
+    "doh-config.json",
+    "doh-providers.json",
+]
+
+if CONFIG["MOZ_BUILD_APP"] == "browser":
+    DIST_SUBDIR = "browser"

services/settings/static-dumps/moz.build

@@ -0,0 +1,7 @@
+# This Source Code Form is subject to the terms of the Mozilla Public
+# License, v. 2.0. If a copy of the MPL was not distributed with this
+# file, You can obtain one at http://mozilla.org/MPL/2.0/.
+
+DIRS += [
+    "main",
+]

services/settings/static-dumps/readme.md

@@ -0,0 +1,14 @@
+# Remote Settings Initial Data
+
+In order to reduce the amount of data to be downloaded on first synchronization,
+a JSON dump from the records present on the remote server can be shipped with the
+release.
+
+The dumps in this directory will NOT automaticaly be kept in sync with remote.
+This is useful for collections that benefit from a default iniital state but
+require dynamism beyond that - e.g. DoH regional configurations. For dumps
+that should automatially be kept in sync with remote, use ../dumps/.
+
+Dumps from dumps/ and static-dumps/ are packaged into the same resource path,
+thus looking the same to the client code and also implying that filenames must
+be unique between the two directories.