my scenario is:
there’s a system under test. Tests basically are doing some commits on which apps that are tested do some more commits and then the state and configuration of the system is validated. On with the next test etc.
Now I need to restore the system to some initial configuration and state before each test. I can’t afford backup and restore because that involves reset of the system which takes too long.
I’m considering using save and load or using rollbacks.
I find load a litte too disruptive, I mean it will basically edit config in one transaction and I don’t know if this won’t have any side-effects on my applications…
… load doesn’t know which of the changes were commited by test code and which were committed by applications so there’s room to potential problems with applications that do not expect to have “their” config modified without reboot.
Is rollback a more gentle way to revert config in this respect ?
I could selectively rollback changes that were commited by test code backwards and that would be the least surprising way to the applications. They should be able to handle that and the system should be reverted to initial state.
Does my reasoning make sense?
Is there a method to remember initial rollback point and then get list of the consecutive rollback points after each test execution, filter the ones commited by CLI or NETCONF and play them back?