Make State load only from scratch and not into existing state#520
Merged
Conversation
tertsdiepraam
force-pushed
the
state-from-scratch
branch
from
March 12, 2026 14:02
798d83c to
6cf5770
Compare
Member
|
What prompted this change? Is this functionality okay to remove? Is the removed behaviour something we never used or needed? |
Contributor
Author
|
I believe that we will never read state after starting up (maybe until we get to high availability but at that point we probably need to reconsider anyway). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This allows us to get rid of some tracking of whether policies and zones are added, retained, removed or updated.