refactor: Remove DeregisterOperatorOperatorSets function #459
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What Changed?
This PR removes
DeregisterOperatorOperatorSets
fromavsRegistry
's chainWriter. The reason of this is that should not be part of SDK, since new flow'sderegisterOperator
should not be accessed from any other location than theAllocationManager
. This is because the register operator method of the new flow can only be called from there (otherwise there will be raised anOnlyAllocationManager()
error). Thus, in the new flow the entry points to the operators registration or deregistration to AVSs should beRegisterForOperatorSets
to register andDeregisterFromOperatorSets
to deregister.Reviewer Checklist