{"version":"2.1.232","anchor":"corrupt-config-reporting-now-also-fires-from-the-storage-rep","canonical_anchor":"corrupt-config-reporting-now-also-fires-from-the-storage-rep","heading":"Corrupt config reporting now also fires from the storage repair path","tier":"notice","area":"Configuration","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/corrupt-config-reporting-now-also-fires-from-the-storage-rep","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Corrupt config reporting now also fires from the storage repair path\n\nCorrupt-config notices, including the restore command hint, now also appear from the repair path.\n\n**What**\n\nThe stderr notices for a missing configuration file and for an existing backup, including the \"You can manually restore it by running: cp\" hint, moved into shared builders and are now emitted by the storage-backed repair path too.\n\n**Details**\n\n- That path writes a backup when a repair actually changed something, and reports the missing file when the storage layer says it is absent.\n\n**Evidence**\n\n`You can manually restore it by running: cp `\n\n- Area: Configuration\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}