With every addition to my config it gets a little less clear to understand. My suggestion would be to create something like Home Assistant does in its yaml, an !include <file|dir> directive that would allow splitting backends and locations into separate files. Considering that both backends and locations should have unique items underneath them, I'd suggest taking their names from from the filenames.
Example:
autorestic.yml
version: 2
global:
forget:
keep-last: 10
keep-daily: 7
keep-weekly: 4
keep-monthly: 12
backends: !include backends/
locations: !include locations/backends/remote.yml
type: rest
path: http://remote.example.com:8086/myserver
key: <redacted>
requirekey: true
rest:
user: myuser
password: <redacted>
locations/important-stuff.yml
from:
- /data/important
to:
- remote
Unfortunately I am not skilled in Go but I'd be more than willing to help testing if this gets implemented.
With every addition to my config it gets a little less clear to understand. My suggestion would be to create something like Home Assistant does in its yaml, an !include <file|dir> directive that would allow splitting backends and locations into separate files. Considering that both backends and locations should have unique items underneath them, I'd suggest taking their names from from the filenames.
Example:
autorestic.ymlbackends/remote.ymllocations/important-stuff.ymlUnfortunately I am not skilled in Go but I'd be more than willing to help testing if this gets implemented.