A lot of verify processes were created to solve issues during the upgrade so they are being refactored us upgrade processes or being removed since are not longer needed.
For this reason we should untie the upgrade process from the execution of the verifiers. Instead We should have a way to check inconsistencies, regenerate permissions, ect anytime (probably when the portal is not opened to public) on demand.
We can keep the framework in this way:
- Untie verify processes from upgrade process
- Allow to execute these processes in read-only mode
- Allow users to execute verify processes on demand (if the execution is in write mode, the affected portal or module has to be unavailable) or with the initial installation of the module (see LPS-101216)