Add uniqueness validation for subnetwork_ranges_list items #3401
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.
What?
Validate uniqueness of subnetwork_name field across subnetwork_ranges_list items.
Why?
An earlier PR had introduced a change to support subnetwork_ranges as a list in the interest of better templated blueprints. However, the uniqueness of the map structure was not maintained in the list, and hence would break when multiple items with same subnetwork_name are passed.
Testing
Passed two items with same subnetwork_name in the list, verified validation was triggered.
Submission Checklist
NOTE: Community submissions can take up to 2 weeks to be reviewed.
Please take the following actions before submitting this pull request.