New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.0.0-rc4 Example for overriding the content-type header of patching operations do not work #1499
Comments
I think that you will need to fix this in the upstream generator: Once the fix is merged there, we can regenerate the client. |
thanks @brendandburns , related to OpenAPITools/openapi-generator#14549 |
The above issue was created a year ago, and given the repo's issue # keeps increasing and now at 4k, I don't have faith this will get addressed soon. I'm okay with my workaround for now, I'll keep this open so ppl can find the workaround here. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
Describe the bug
The configuration passed into the patching APIs do not honor the middleware overrides.
The generated code does not even look at the passed in configuration for the middlewares, it only looks at the middlewares of its member configuration object.
e.g.
** Client Version **
1.0.0-rc4
** Server Version **
1.25.1
To Reproduce
Steps to reproduce the behavior:
patchNamespacedStatefulSet
with the configuration overriding with the middleware.Expected behavior
The middleware should be called to override the request.
** Example Code**
see https://github.com/kubernetes-client/javascript/blob/62e5ab1701cb5659656f1941ef11eb748e626c25/examples/patch-example.js
Environment (please complete the following information):
Additional context
Related to #1398
Workaround
The text was updated successfully, but these errors were encountered: