THREESCALE-11879: Order backend API mapping rules - #4100
Merged
Conversation
mayorova
force-pushed
the
fixed-order-backend-mapping-rules
branch
3 times, most recently
from
June 30, 2025 15:31
cf41b02 to
8332cb3
Compare
mayorova
force-pushed
the
fixed-order-backend-mapping-rules
branch
from
June 30, 2025 20:22
8332cb3 to
8ca4412
Compare
lvillen
approved these changes
Jul 2, 2025
josemigallas
approved these changes
Jul 2, 2025
This was referenced Jul 2, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 this PR does / why we need it:
There was no defined order on backend APIs, so the order was defined by the database, and it is error-prone and unpredictable.
Which issue(s) this PR fixes
https://issues.redhat.com/browse/THREESCALE-11879
Verification steps
The mapping rules should be ordered by position at least in:
/apiconfig/services/{SERVICE_ID}/proxy_configs?environment=staging/p/admin/backend_apis/{BACKEND_API_ID}/mapping_rules/admin/api/backend_apis/{BACKEND_API_ID}/mapping_rules.jsonSpecial notes for your reviewer: