Prevent duplicate network ranges per customer (#681) #682
+286
−3
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.
Closes #681
Summary
This PR adds application-level validation to ensure a single customer cannot register the same network range more than once. The check uses exact equality on HostNetworkGroup values (as requested in the issue) and runs both when inserting a new Customer and when updating an existing Customer's networks.
What changed
src/tables/customer.rs
CHANGELOG.md
Why
The system previously allowed registering identical network ranges under the same customer when network names differed. This change enforces uniqueness per-customer to prevent duplicate network entries and the potential confusion or conflicts they cause. The validation is implemented at the application level (no DB migration) and uses exact equality semantics as specified.
Notes
Related
Issue: #681