The node-zones fact was a path; the local=/address= syntax lived in the control plane. It is dnsmasq's configuration language, so it moves into dnsmasq's manifest as a template over the roster ({{.Suffix}}, {{range .Machines}}). The mesh renders it and reads none of it. Output is unchanged.
Lands together with the mesh-controller PR of the same name — the two are one schema step (facts became {path, template}), and dnsmasq is the only catalog module using facts.
The `node-zones` fact was a path; the `local=`/`address=` syntax lived in the control plane. It is dnsmasq's configuration language, so it moves into dnsmasq's manifest as a template over the roster (`{{.Suffix}}`, `{{range .Machines}}`). The mesh renders it and reads none of it. Output is unchanged.
Lands together with the mesh-controller PR of the same name — the two are one schema step (facts became `{path, template}`), and dnsmasq is the only catalog module using facts.
The node-zones fact was a path; the local=/address= syntax lived in the
control plane. It is dnsmasq's configuration language, so it moves into
dnsmasq's manifest as a template over the roster. The mesh renders it; it
reads none of it. Output is unchanged.
Lands with mesh-controller's ADR 0120 change — the two are one schema step.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The
node-zonesfact was a path; thelocal=/address=syntax lived in the control plane. It is dnsmasq's configuration language, so it moves into dnsmasq's manifest as a template over the roster ({{.Suffix}},{{range .Machines}}). The mesh renders it and reads none of it. Output is unchanged.Lands together with the mesh-controller PR of the same name — the two are one schema step (facts became
{path, template}), and dnsmasq is the only catalog module using facts.