fix(standalone): lack of configuration validation in api#12424
Merged
Conversation
nic-6443
reviewed
Jul 14, 2025
nic-6443
reviewed
Jul 14, 2025
nic-6443
reviewed
Jul 14, 2025
membphis
previously approved these changes
Jul 15, 2025
membphis
left a comment
Member
There was a problem hiding this comment.
LGTM
only one minor issue(about code style)
nic-6443
previously approved these changes
Jul 15, 2025
bzp2010
requested changes
Jul 15, 2025
AlinsRan
force-pushed
the
fix/standalone-api-schema
branch
from
July 16, 2025 00:55
358c5d8 to
a2e22e8
Compare
AlinsRan
force-pushed
the
fix/standalone-api-schema
branch
from
July 16, 2025 01:06
a2e22e8 to
340782f
Compare
bzp2010
reviewed
Jul 16, 2025
bzp2010
reviewed
Jul 16, 2025
nic-6443
approved these changes
Jul 17, 2025
bzp2010
approved these changes
Jul 18, 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
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:
In standalone mode, the lack of code validation related to admin API results in incorrect configurations being able to pass validation, as shown in the following example:
When configuring an invalid upstream:
Expect:
Actual:
When configuring an invalid plugin
Expect:
Actual:
Checklist