-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
ValidatingWebhookConfigurationOperationsImpl should be a NonNamespaceOperation #1387
Comments
@leogps : Could you please create a quick PR to resolve this? |
We need to add this method somehow, but it's autogenerated: Lines 38 to 41 in a33f01b
|
I see that the implementation makes use of jsonschema2pojo to auto-generate the pojos and seems like the Handler and the OperationImpl are also auto-generated. I am not sure how exactly this is accomplished. The ideal solution might be to fix the auto-generate logic to include the method properly. |
@leogps : I think you're right. If we copy that class from target to dsl, and make changes onto it, it gets overridden. let me create a quick PR myself |
…ld be a NonNamespaceOperation
…ld be a NonNamespaceOperation
…ld be a NonNamespaceOperation
Just checking if the fix is available in a newer build? |
Yeah, you can verify via building snapshot from master
मंगल, 26 मार्च 2019, 08:57 को leogps <notifications@github.com> ने लिखा:
… Just checking if the fix is available in a newer build?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1387 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANMZAmiAVBI_gujXFaPxr3-oUrOTS0ixks5vaZOzgaJpZM4bgihX>
.
|
When dealing with ValidatingWebhookConfiguration, namespace should not be specified in the url.
However, when creating a ValidatingWebhookConfiguration throws an exception as it ends up appending namespace to the url.
The following code constructs the URL incorrectly.
Constructs:
Instead of:
Reproducible with: kubernetes-client-4.1.2.jar
The text was updated successfully, but these errors were encountered: