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 is more of an experiment that might work out, might not.
I've been worn down by how incredibly complicated our route (subnet route) and particularly HA route logic is. the database part has pointers to state that should be way out of reach (connected nodes) and so on.
We also store a bunch of info in the database that we dont need to persist:
Base premise:
There is gonna be part of this code which isnt particularly "efficient", but that can be optimised later. I doubt it would be worse than the current setup anyways. Make it work, then make it fast.
TODO:
New CLI should be a lot easier to reason about:
List all (or specific) routes:
Approval of routes will overwrite all, so you define the ones you want,
you can approve routes that are not yet defined: