Currently it must be a separate file, but long term we plan to support a single file. That's why there is a root key "cache" which otherwise doesn't seem useful. We'll need some infrastructure changes for that, primarily a single place to read configuration files which then dispatches based on the top level key to the appropriate handler.
-----Original Message----- From: James Peach <[email protected]> Sent: Tuesday, December 12, 2023 1:40 AM To: [email protected] Subject: Re: YAML update for cache configuration. > On 6 Dec 2023, at 12:35 pm, Alan Carroll <[email protected]> wrote: > > As part of the ongoing conversion to YAML for configuration files, Masaori > and I have been collaborating a configuration file format which combines > “volume.config” and “storage.config” for the cache, because we think it’s > always been a bit silly for these to be separate files. Documentation for the > new format > > ============== > cache.yaml > ============== > > > .. configfile:: cache.yaml Does it have yo be a separate file? You could put all this config in records.yaml … J
