Warn when using a non-empty spec.Servers
#883
Merged
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.
It's a fairly common mistake when using the OpenAPI request validation
filter from kin-openapi to receive
no matching operation was found
errors if using the
servers
directive in your OpenAPI specification.This is a valid usescase, but you may not always want to be enforcing
the validation that the
Host
header matches one of theservers
mentioned in your specification.
This makes it clearer to operators that there may be a configuration
issue here, as a way to avoid as many folks falling into the same trap
that many have before.
This also provides an option to silence the warning, as logging out can
be annoying and costly.
Closes #882.