custom_objects_api should have a method list_custom_object_for_all_namespaces
#268
Comments
|
Seems like we need to add another gen/openapi/custom_objects_spec.json Line 47 in 37662b2 But
— https://swagger.io/docs/specification/paths-and-operations/ How can we do it? |
|
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
added a commit
to davidxia/gen
that referenced
this issue
Sep 16, 2024
for the API path `/apis/{group}/{version}/{plural}`.
We define a new key `/apis/{group}/{version}/{plural}#[U+200E]`
in `custom_objects_spec.json` to work around this limitation.
> 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
We use the hair space empty character to visually hide this path param from the
Swagger UI.
closes kubernetes-client#268
Work around was taken from [here][1].
[1]: OAI/OpenAPI-Specification#182 (comment)
|
@brendandburns thanks! I made a PR #269 |
davidxia
added a commit
to davidxia/gen
that referenced
this issue
Sep 16, 2024
for the API path `/apis/{group}/{version}/{plural}`.
We define a new key `/apis/{group}/{version}/{plural}#[U+200E]`
in `custom_objects_spec.json` to work around this limitation.
> 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
We use the hair space empty character to visually hide this path param from the
Swagger UI.
may resolve kubernetes-client#268
Work around was taken from [here][1].
[1]: OAI/OpenAPI-Specification#182 (comment)
davidxia
added a commit
to davidxia/gen
that referenced
this issue
Sep 16, 2024
for the API path `/apis/{group}/{version}/{plural}`.
We define a new key `/apis/{group}/{version}/{plural}#[U+200E]`
in `custom_objects_spec.json` to work around this limitation.
> 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
We use the hair space empty character to visually hide this path param from the
Swagger UI.
addresses kubernetes-client#268
Work around was taken from [here][1].
[1]: OAI/OpenAPI-Specification#182 (comment)
k8s-ci-robot
pushed a commit
that referenced
this issue
Sep 18, 2024
for the API path `/apis/{group}/{version}/{plural}`.
We define a new key `/apis/{group}/{version}/{plural}#[U+200E]`
in `custom_objects_spec.json` to work around this limitation.
> 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
We use the hair space empty character to visually hide this path param from the
Swagger UI.
addresses #268
Work around was taken from [here][1].
[1]: OAI/OpenAPI-Specification#182 (comment)
|
Closed via #269 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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_namespacescalls endpoint/apis/{group}/{version}/{plural}to get custom objects in all namespaces.— kubernetes-client/python#1377 (comment)
The text was updated successfully, but these errors were encountered: