-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Dry run generate config with diff against current config #185
Comments
Pathvector stores the output of a dry run in $ pathvector gen --dry-run
INFO[0000] Starting Pathvector 6.3.2
INFO[0005] BIRD config validation passed
INFO[0005] Processed 8 peers in 5s
$ diff /var/run/pathvector/cache/ /etc/bird/
Only in /etc/bird/: AS34553_LGAS34553NET.conf
diff /var/run/pathvector/cache/bird.conf /etc/bird/bird.conf
1c1
< # Update time: 1689659925
---
> # Update time: 1689659872
Only in /etc/bird/: envvars
Only in /etc/bird/: protocols.json If there were to be config changes other than removing a peer, you'd see the individual line diffs too. |
natesales
added a commit
that referenced
this issue
Jul 18, 2023
I didn't realise this, thanks! Should this perhaps be documented somewhere? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there is a "dry run" option for pathvector, but it would be lovely to dry-run pathvector generate and have pathvector show the diff between the files which would have been generated and the current config. This would help to see the details of how the bird config changes when a new config or even a new pathvector version is used.
The text was updated successfully, but these errors were encountered: