Configs can't be managed when Git is offline
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the current sr3_push flow and compare it with the v2 sr_push behavior described in the issue. Investigate how the Git repository is transferred to cluster nodes when the Git server is unavailable, including how rsync could exclude gitignored files and local branches. Done means configs can be pushed during Git-server outages without requiring manual edits or scp.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100