We have a separate set of databases that we use to generate SIS imports for our Canvas test instance. Whenever the test instance is reset with production data, we have to bring it back in line with our test data: generate a new API key, install it in various places, reconcile the user records, and do a full SIS update. We also have to re-create any admin accounts that we provide to developers in the test instance. Plus, we have to reinstall our LTI tool so that it points to the LTI tool test instance. So it appears that the test instance reset creates extra work for us, and I'm not aware of any benefit that it is providing.
I'm considering asking Instructure not to perform this reset for our Canvas test instance. Are there any pros or cons to this plan that I should take into account?