You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When kusk generates operation-specific ingresses from a swagger2 specification, the (optional) basePath in that definition gets lost. For example if my Swagger2 definition contains
basePath: "/api"
and an operation-level override for some operation:
x-kusk:
disabled: true
the generated ingresses are missing the leading "/api" path segment - which I have to add manually;
When kusk generates operation-specific ingresses from a swagger2 specification, the (optional) basePath in that definition gets lost. For example if my Swagger2 definition contains
and an operation-level override for some operation:
the generated ingresses are missing the leading "/api" path segment - which I have to add manually;
The text was updated successfully, but these errors were encountered: