{"version":"2.1.228","anchor":"on-disk-stores-can-be-served-from-a-new-storage-backend","canonical_anchor":"on-disk-stores-can-be-served-from-a-new-storage-backend","heading":"On-disk stores can be served from a new storage backend","tier":"soon","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/on-disk-stores-can-be-served-from-a-new-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### On-disk stores can be served from a new storage backend\n\nConfig, plugin and marketplace files can be read from a new storage backend when it's provisioned.\n\n**What**\n\nFeedback drafts, workflow journals, the installed plugins file, marketplace manifests and catalogs, and the global config all gained a path through a v5 storage backend, taken only when that backend and a valid key are present on the call. Nothing in this build forces it on, so which path runs depends on how the backend is provisioned. Everything falls back to ordinary files otherwise.\n\n**Details**\n\n- Feedback drafts support listing, reading the tail in batches, and deletion.\n- Workflow journals append records behind a cursor that is required to move forward, and log when it does not.\n- Backend failures are logged with the error code and degrade to previous behaviour rather than throwing.\n\n**Evidence**\n\n`LocalFileJournal: journal read cursor failed to advance`\n\n- Area: Internals\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}