In v2, sr_push would commit the config file to git and scp it to each node. This allowed configs to be pushed when the Git server is down.
With sr3_tools, the servers pull configs from the Git server, and there's no automated way to update the configs on the nodes if the server isn't available. In emergencies, users could manually edit the configs on each node, or scp changes by hand.
A possible solution would be to re-write sr3_push to rsync the Git repo from the workstation to all the nodes in the cluster. Some extra work would need to be done to avoid rsyncing gitignored files and local branches.
In v2,
sr_pushwould commit the config file to git and scp it to each node. This allowed configs to be pushed when the Git server is down.With sr3_tools, the servers pull configs from the Git server, and there's no automated way to update the configs on the nodes if the server isn't available. In emergencies, users could manually edit the configs on each node, or scp changes by hand.
A possible solution would be to re-write
sr3_pushto rsync the Git repo from the workstation to all the nodes in the cluster. Some extra work would need to be done to avoid rsyncing gitignored files and local branches.