Reduce duplication between scratchnet configs #2942
Description
> sha256sum cluster/deployment/scratchnet*/config.yaml
ee8ade1d837fa7001911b89795b111ce2569e2a6f89b03c313ce7b53bd00928b cluster/deployment/scratchneta/config.yaml
ee8ade1d837fa7001911b89795b111ce2569e2a6f89b03c313ce7b53bd00928b cluster/deployment/scratchnetb/config.yaml
ee8ade1d837fa7001911b89795b111ce2569e2a6f89b03c313ce7b53bd00928b cluster/deployment/scratchnetc/config.yaml
ee8ade1d837fa7001911b89795b111ce2569e2a6f89b03c313ce7b53bd00928b cluster/deployment/scratchnetd/config.yaml
ee8ade1d837fa7001911b89795b111ce2569e2a6f89b03c313ce7b53bd00928b cluster/deployment/scratchnete/config.yaml
There's got to be a better way.
Sadly we can't just use cluster/deployment/config.yaml because that one is also used by prod clusters.
"Symlinks" sounds compelling, but will likely confuse our submodules-and-flux workflows.
So I think I'd go for some new config option (in config.yaml) that allows configuring an extra xyz-config.yaml to load and merge with? And configure only this inside each individual scratchnet?