By: Tom Sydney Kerckhove <syd@cs-syd.eu>
Let the deployment do the downloading around itself The four steps are download, check, deploy, download again, and the check is the one that happens when the deployment is built rather than when it is run: the three downloaded files are a record of the router, committed, and read the way a golden file is read. So the command does the other three. Before touching anything it asks the router what it is and refuses if the answer is not the export the checks read, because a check that answered about a router that has since been changed is worse than no check at all. Afterwards it asks again and prints what changed on the router, which is a different question from what it was told to change, and the one worth asking while you are still looking. With record set it writes the three files back, so the next check reads the router as this deployment left it. record is validated before the reset rather than after the import, since a deployment that has already run cannot be told to go and be run somewhere else.