fix(api7): use exact search to determine gateway group #360
+1
−0
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
Currently, gateway group id uses fuzzy search on the
name
, which may select the wrong gateway group when prefixes are the same.This PR addresses this issue. When users employ API7 versions supporting exact search, the ADC will perform an exact match search for gateway groups to verify the ID. For versions lacking exact search capability, it automatically falls back to the current implementation, continuing to use fuzzy search to determine the gateway group.
Checklist