refactor: separate model for IPSec Security Policies #1679
Merged
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.
The previous model of configuring SPs inside SPD is now deprecated. In practice the content of SPD is changing very frequently and using a single model with all SPs inside is therefore neither convenient nor efficient. A new model SecurityPolicy was added which allows to configure each SP as a separate proto message instance. Although the new model is still backward-compatible with the old one, request to configure SP through the SPD model will return an error (invalid config).
Also fixed couple of bugs that were present in the original implementation and tested the implementation with real-world configurations.