API Errors: #/paths: Additional properties not allowed:
up vote
0
down vote
favorite
I have a service on node.js, which is run locally and when I build it via docker (which is the way we deploy). But on kubernetes environment after deploy this service I am getting the following error:
API Errors:
#/paths: Additional properties not allowed:
1 error and 0 warnings
I have overlooked the whole possible answers here and in the google, but have not found any related to such empty "paths" (usually #/paths
is more logical and after allowed:
is written something).
swagger access
add a comment |
up vote
0
down vote
favorite
I have a service on node.js, which is run locally and when I build it via docker (which is the way we deploy). But on kubernetes environment after deploy this service I am getting the following error:
API Errors:
#/paths: Additional properties not allowed:
1 error and 0 warnings
I have overlooked the whole possible answers here and in the google, but have not found any related to such empty "paths" (usually #/paths
is more logical and after allowed:
is written something).
swagger access
What's the question?
– Ace
Nov 22 at 14:39
@Ace question is that service is not run, because of this error. But I have found what's wrong, somehow there was anundefined
route, which is actually result of silent error in the question.
– Oleksandr Tserkovnyi
Nov 24 at 1:15
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a service on node.js, which is run locally and when I build it via docker (which is the way we deploy). But on kubernetes environment after deploy this service I am getting the following error:
API Errors:
#/paths: Additional properties not allowed:
1 error and 0 warnings
I have overlooked the whole possible answers here and in the google, but have not found any related to such empty "paths" (usually #/paths
is more logical and after allowed:
is written something).
swagger access
I have a service on node.js, which is run locally and when I build it via docker (which is the way we deploy). But on kubernetes environment after deploy this service I am getting the following error:
API Errors:
#/paths: Additional properties not allowed:
1 error and 0 warnings
I have overlooked the whole possible answers here and in the google, but have not found any related to such empty "paths" (usually #/paths
is more logical and after allowed:
is written something).
swagger access
swagger access
asked Nov 22 at 14:11
Oleksandr Tserkovnyi
136
136
What's the question?
– Ace
Nov 22 at 14:39
@Ace question is that service is not run, because of this error. But I have found what's wrong, somehow there was anundefined
route, which is actually result of silent error in the question.
– Oleksandr Tserkovnyi
Nov 24 at 1:15
add a comment |
What's the question?
– Ace
Nov 22 at 14:39
@Ace question is that service is not run, because of this error. But I have found what's wrong, somehow there was anundefined
route, which is actually result of silent error in the question.
– Oleksandr Tserkovnyi
Nov 24 at 1:15
What's the question?
– Ace
Nov 22 at 14:39
What's the question?
– Ace
Nov 22 at 14:39
@Ace question is that service is not run, because of this error. But I have found what's wrong, somehow there was an
undefined
route, which is actually result of silent error in the question.– Oleksandr Tserkovnyi
Nov 24 at 1:15
@Ace question is that service is not run, because of this error. But I have found what's wrong, somehow there was an
undefined
route, which is actually result of silent error in the question.– Oleksandr Tserkovnyi
Nov 24 at 1:15
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432842%2fapi-errors-paths-additional-properties-not-allowed%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What's the question?
– Ace
Nov 22 at 14:39
@Ace question is that service is not run, because of this error. But I have found what's wrong, somehow there was an
undefined
route, which is actually result of silent error in the question.– Oleksandr Tserkovnyi
Nov 24 at 1:15