{"version":"2.1.234","anchor":"credentials-and-transcript-tails-can-be-read-through-the-sto","canonical_anchor":"credentials-and-transcript-tails-can-be-read-through-the-sto","heading":"Credentials and transcript tails can be read through the storage backend","tier":"soon","area":"Storage Backend","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/credentials-and-transcript-tails-can-be-read-through-the-sto","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Credentials and transcript tails can be read through the storage backend\n\nCredentials and transcript tails can be read from the new storage backend, but the flag is off.\n\n**What**\n\nStored credentials and the tail of a transcript being resumed can now be read and written through the alternative storage backend rather than directly from disk. Both are selected only when the `tengu_hover_rest` flag is on, which it is not without a server value, so this build uses the existing file paths.\n\n**Details**\n\n- The credentials adapter wraps read, strict read, write and delete, and maps a refused symlink or a failed read to a single sentinel value. Writing still prints the same \"Warning: Storing credentials in plaintext.\" notice as before.\n- Resume does a backend tail read plus a stat, allowing for a partially written last record, and falls back to reading the raw file with a warning if the read or the stat fails or the backend throws.\n\n**Evidence**\n\n`Warning: Storing credentials in plaintext.`, `hydrate tail: backend tail read failed`\n\n- Flag `tengu_hover_rest`: Off in both readings (read for one account on one subscription tier against v2.1.234; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Storage Backend\n- Names: `tengu_hover_rest`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}