Allow re-starting a graph node on a new chain.

[xenoliss]

Do you want to request a feature or report a bug?
Feature

What is the current behavior?
I'm running a private chain locally that I restart sometimes. After a restart, the graph-node complains that the state of the chain is not the same as it was previously. To remediate that I have to clear the docker volumes and restart the node.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

What is the expected behavior?
It would be super helpful to have an option that, when specified, simply starts the graph node and start indexing on the new chain even if the state does not match with the previous registered one.

[schmidsi]

This might be solved with an env-var/configuration variable. Thanks for the report @xenoliss! Good point.

[github-actions]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.

[fordN]

Graphman now has support for updating the genesis block of a chain, so you can move to a different chain if needed.