When writing a config file one may be tempted to use nested templates like these, where one snippet builds on top of another:
machine_snippets:
cfg-template: &cfg-template
setup_template:
path: /etc/forrest/templates/generic
parameters:
RUNNER_VERSION: "2.318.0"
RUNNER_HASH: "28ed88e4cedf0fc93201a901e392a70463dbd0213f2ce9d57a4ab495027f3e2f"
os-debian: &os-debian
<< : *cfg-template
base_image: /srv/forrest/images/debian-12-generic-amd64.raw
debian-small: &debian-small
<< : *os-debian
cpus: 4
disk: 16G
ram: 4G
This does however not work due to faulty handling of nested merges in the yaml crate used.
See sebastienrousseau/serde_yml#14 and sebastienrousseau/serde_yml#15 for more information.
When writing a config file one may be tempted to use nested templates like these, where one snippet builds on top of another:
This does however not work due to faulty handling of nested merges in the yaml crate used.
See sebastienrousseau/serde_yml#14 and sebastienrousseau/serde_yml#15 for more information.