You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
:param str group: The custom resource's group name (required)
2248
2248
:param str version: The custom resource's version (required)
2249
-
:param str plural: The custom resource's plural name. For TPRs this would be lowercase plural kind. (required)
2249
+
:param str resource_plural: The custom resource's plural name. For TPRs this would be lowercase plural kind. (required)
2250
2250
:param str pretty: If 'true', then the output is pretty printed.
2251
2251
:param bool allow_watch_bookmarks: allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
2252
2252
:param str _continue: The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
:param str group: The custom resource's group name (required)
2285
2285
:param str version: The custom resource's version (required)
2286
-
:param str plural: The custom resource's plural name. For TPRs this would be lowercase plural kind. (required)
2286
+
:param str resource_plural: The custom resource's plural name. For TPRs this would be lowercase plural kind. (required)
2287
2287
:param str pretty: If 'true', then the output is pretty printed.
2288
2288
:param bool allow_watch_bookmarks: allowWatchBookmarks requests watch events with type \"BOOKMARK\". Servers that do not implement bookmarks may ignore this flag and bookmarks are sent at the server's discretion. Clients should not assume bookmarks are returned at any specific interval, nor may they assume the server will send any BOOKMARK event during a session. If this is not a watch, this field is ignored. If the feature gate WatchBookmarks is not enabled in apiserver, this field is ignored.
2289
2289
:param str _continue: The continue option should be set when retrieving more results from the server. Since this value is server defined, clients may only use the continue value from a previous query result with identical query parameters (except for the value of continue) and the server may reject a continue value it does not recognize. If the specified continue value is no longer valid whether due to expiration (generally five to fifteen minutes) or a configuration change on the server, the server will respond with a 410 ResourceExpired error together with a continue token. If the client needs a consistent list, it must restart their list without the continue field. Otherwise, the client may send another list request with the token received with the 410 error, the server will respond with a list starting from the next key, but from the latest snapshot, which is inconsistent from the previous list results - objects that are created, modified, or deleted after the first list request will be included in the response, as long as their keys are after the \"next key\". This field is not supported when watch is true. Clients may start a watch from the last resourceVersion value returned by the server and not miss any modifications.
@@ -2313,7 +2313,7 @@ def list_custom_object_for_all_namespaces_with_http_info(self, group, version, p
2313
2313
all_params= [
2314
2314
'group',
2315
2315
'version',
2316
-
'plural',
2316
+
'resource_plural',
2317
2317
'pretty',
2318
2318
'allow_watch_bookmarks',
2319
2319
'_continue',
@@ -2350,10 +2350,10 @@ def list_custom_object_for_all_namespaces_with_http_info(self, group, version, p
0 commit comments