-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Lifecycle finalized events triggered before starting the node #1210
base: main
Are you sure you want to change the base?
Conversation
We should finalize/migrate ACL before we start the node. Also useful for other cases when we need to have these in the final data to make sure wwe do not change after someone already tries to connect.
Review changes with SemanticDiff. Analyzed 3 of 3 files. Overall, the semantic diff is 2% smaller than the GitHub diff.
|
/** | ||
* Emits when the node is finalized and goes online next | ||
*/ | ||
get finalized() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if we can avoid adding the event, it doesn't seem very general purpose. Why do we initialize AccessControlManager when the node comes online rather than when AccessControlServer initializes?
Is it just because FabricManager isn't available until the node is online, and we need that to perform the upgrade from 0.7? In my ClientNode branch I pulled FabricManager initialization into node startup, so if that's the problem maybe I could push that so AccessManager initialization could happen sooner.
We should finalize/migrate ACL before we start the node. Also useful for other cases when we need to have these in the final data to make sure wwe do not change after someone already tries to connect.