<h1 dir="auto">Summary of the new feature/enhancement</h1>
<p dir="auto">Today, custom-zone-sets are stored in the zones-settings.json file, along with app-zone-history and devices trees. This makes it difficult to backup or share configurations between people / computers.</p>
<h1 dir="auto">Proposed Solution</h1>
<p dir="auto">Propose moving custom-zone-sets into a directory where each custom zone setting is a separate file.</p>
<h1 dir="auto">Benefits</h1>
<ul dir="auto">
<li>back up and restore custom zone sets</li>
<li>sharing custom zone sets or specific templates with community</li>
</ul>
<p dir="auto">Having the app history in the same file of the zones settings has some drawbacks:</p>
<ul dir="auto">
<li>it contains sensitive data and makes more complicated to report the zone settings without it</li>
<li>we need to make changes to the app history schema and that work should not effect the zones settings code path</li>
<li>since we have to persist the app history data more frequently than the zone settings, it's kind of pointless to process the zone settings every time we need to read/write the app history</li>
</ul>