custom_objects_api should have a method `list_custom_object_for_all_namespaces`

[davidxia]

What is the feature and why do you need it:

Similar to the core_v1_api like list_pod_for_all_namespaces, the custom_objects_api should have a method list_custom_object_for_all_namespaces.

Describe the solution you'd like to see:

list_custom_object_for_all_namespaces calls endpoint /apis/{group}/{version}/{plural} to get custom objects in all namespaces.

Although list_custom_object_for_all_namespaces and list_cluster_custom_object happens to talk to the same API endpoint, it may be better to have a list_custom_object_for_all_namespaces method for documentation purpose. kubernetes-client/java#941 (comment) is the right way to fix this issue. Since this issue affects multiple clients, would you mind filing an issue in https://github.com/kubernetes-client/gen about fixing the openapi spec?

— kubernetes-client/python#1377 (comment)

[davidxia]

Seems like we need to add another "get" with {"operationId": ["listCustomObjectForAllNamespaces", ...} here?

gen/openapi/custom_objects_spec.json

Line 47 in 37662b2

"/apis/{group}/{version}/{plural}": {

But

OpenAPI defines a unique operation as a combination of a path and an HTTP method. This means that two GET or two POST methods for the same path are not allowed

— https://swagger.io/docs/specification/paths-and-operations/

How can we do it?

[brendandburns]

We could consider using the hashtag approach as described here:

OAI/OpenAPI-Specification#182 (comment)

That may work. In general that discussion has numerous people trying to solve similar issues.

[davidxia]

@brendandburns thanks! I made a PR #269

[brendandburns]

Closed via #269