Switch routing policies fix #35
Merged
+14,936
−10,077
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull request overview
This PR corrects the ordering and requirements for routing policy terms in the OpenAPI specification. The changes ensure alphabetical ordering of enum values and add a required name field to switch routing policy terms.
Key changes:
- Alphabetized the
gw_routing_policy_term_matching_protocol_enumvalues to match standard enum ordering conventions - Added
nameas a required field forsw_routing_policy_termschema
Reviewed changes
Copilot reviewed 2 out of 5 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| workdir/openapi.yaml | Updated enum ordering and added required name field to switch routing policy term schema |
| mist.openapi.yaml | Applied identical changes as workdir/openapi.yaml to maintain consistency |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
tmunzer
approved these changes
Dec 22, 2025
- getSiteInsightMetricsForGateway - getSiteInsightMetricsForMxEdge - getSiteInsightMetricsForSwitch
remove useless `site_id` query parameter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.