Skip to content
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

Clean up/Data Lifecycle of TssEncryptionKey in State #16570

Open
Tracked by #14542
derektriley opened this issue Nov 12, 2024 · 0 comments
Open
Tracked by #14542

Clean up/Data Lifecycle of TssEncryptionKey in State #16570

derektriley opened this issue Nov 12, 2024 · 0 comments
Labels
Platform Tickets pertaining to the platform

Comments

@derektriley
Copy link
Contributor

derektriley commented Nov 12, 2024

Background
When a node id is not present in any of the active rosters or a candidate roster, the entry for that node id should be removed. This cleanup task should trigger any time there is a candidate or active roster state change.

Look at usages of WritableRosterStore::putCandidateRoster, putActiveRoster, removeRoster

Acceptance Criteria

  • All code locations where active roster or candidate rosters are changed, need to check and trigger the cleanup task.
  • Unit or Hapi Tests which verify the node id is removed from the TssEncrpytionKey map in state when the cleanup task occurs.

Dependencies
#16555

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Platform Tickets pertaining to the platform
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant