API ApiextensionsV1API_deleteCustomResourceDefinition wrong return type

[hirishh]

Hello,

I know that in general with the generic api I can workaroud all the model-cjson converting issues, but I still think it's important to report all the bugs.

I was playing with ApiextensionsV1API.h apis, and in particular with ApiextensionsV1API_deleteCustomResourceDefinition (https://github.com/kubernetes-client/c/blob/master/kubernetes/api/ApiextensionsV1API.h#L31)

Every call to this method returns a NULL v1_status_t* so I started to dig deeper.
This call should return a v1_custom_resource_definition_t and not a v1_status_t. That's why parsing is failing.

Best

[brendandburns]

Unfortunately, this is expected behavior. The RESTful API has multiple return types, but for now the code generator only generates a single return type. It is possible that we could update the code generator to return a union or something like that, but until that happens you will need to work around this. It is a common problem across many clients.

[brendandburns]

For clarity, it returns a v1_status_t when it takes longer than a certain time (async) and the actual object when the delete happens quickly (sync)

[hirishh]

Ohhh ok, I didn't know about that. It's good to know! Thanks!

[brendandburns]

fwiw, there are various discussions of this, eg kubernetes-client/java#86

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten