{"version":"2.1.235","anchor":"remote-settings-can-now-be-primed-from-the-storage-backend-i","canonical_anchor":"remote-settings-can-now-be-primed-from-the-storage-backend-i","heading":"Remote settings can now be primed from the storage backend instead of a disk probe","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/remote-settings-can-now-be-primed-from-the-storage-backend-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Remote settings can now be primed from the storage backend instead of a disk probe\n\nRemote settings can now be loaded from a storage-backend view instead of only probing disk\n\nA new backend view subscribes to a key in storage v5 to prime remote settings, reads it under a size cap, refreshes on updates, and falls back to the old disk probe if the watch fails, the cache is oversized, the cache file is symlinked, or the account changes mid-flight. Each transition is logged.\n\nAlso new: `policyHelpers` entries armed from remote config are revoked if that arming is withdrawn while a run is in progress, and a status warning now surfaces when a remote entry was not run. This sits behind the `tengu_hover_rest` gate, which v2.1.234 compiled on by default; the flag server returned it off for both this site's account and the anonymous baseline, and no reading has been taken under this release yet.\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.235; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}