feat: subordinate protocol validation and deletion check #12796
Closed
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.
Description
Which issue(s) this PR fixes:
Fixes #6939
This PR implements subordinate (parent–child) relationship validation for stream routes in the Admin API, as proposed in issue #6939. Previously, stream routes could reference a superior_id without any validation, which could lead to invalid configurations, broken dependencies, and runtime routing errors.
This change ensures that:
• Any referenced superior stream route must exist.
• The protocols between subordinate and superior routes must match.
• A superior stream route cannot be deleted if it is still referenced by another route.
Also added some test cases for this update.
Checklist