-
Notifications
You must be signed in to change notification settings - Fork 110
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
Test that old zebrad.toml files still work #4625
Comments
I am unsure if we should use cargo insta, snapshots and how. 1- If you make a snapshot of the config, you have to remove the header meta data to convert it to a real config file that zebra can use to start. Here is what i think we should do:
If there are breaking changes to the config in the future the old config will fail to start zebra, we will then have to update the stored old config file to make the test pass. That way we will know before merging and can notify users (I think is the only thing we can do if the new config has breaking changes and we still want to go ahead with them). Let me know how do you see it, or if we want to use snapshots please explain the workflow a bit more. Thanks. |
This seems better to me, I'll edit the ticket. |
We also need to make sure that new config fields are added to the test config. |
Can you clarify the git part please ? Thanks! |
I meant "in the Zebra git repository", I've added that to the ticket. |
Motivation
We want to make sure that we don't accidentally break the config format.
Designs
zebrad generate
output to a test folder in the Zebra git repositoryzebrad start
using the config from the Zebra git repositoryWe already have a test that launches using a freshly generated config.
The text was updated successfully, but these errors were encountered: