Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configs can't be managed when Git is offline #18

Open
reidsunderland opened this issue Feb 12, 2024 · 0 comments
Open

Configs can't be managed when Git is offline #18

reidsunderland opened this issue Feb 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@reidsunderland
Copy link
Member

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.

@reidsunderland reidsunderland added the enhancement New feature or request label Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant