Closed Gu1nness closed 2 months ago
But is it implementation agnostic. i.e. if we go with v3 on MongoDB K8s but v2 on MongoDB VM with this change still stand?
This code does not care about the actual upgrade but only the checks. If V3 needs some update, we can always overload the functions that would need a fix. This only ports the minimal amount of code to make the pre upgrade hooks work :)
My concern is that functions in AbstractUpgrade
won't be used in K8s , since ideally those upgrade specific functions will be in a lib for v3. But I trust you!
Issue
Upgrade
class is substrate agnostic and should be reused.Solution