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
Copy file name to clipboardExpand all lines: kubernetes/lib/Kubernetes/OpenAPI/API/CustomObjects.hs
+20Lines changed: 20 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -550,6 +550,11 @@ instance HasOptionalParam ListClusterCustomObject Pretty where
550
550
applyOptionalParam req (Pretty xs) =
551
551
req `addQuery` toQuery ("pretty", Just xs)
552
552
553
+
--| /Optional Param/ "allowWatchBookmarks" - 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.
req `addQuery` toQuery ("allowWatchBookmarks", Just xs)
557
+
553
558
-- | /Optional Param/ "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.
@@ -575,6 +580,11 @@ instance HasOptionalParam ListClusterCustomObject ResourceVersion where
575
580
applyOptionalParam req (ResourceVersion xs) =
576
581
req `addQuery` toQuery ("resourceVersion", Just xs)
577
582
583
+
--| /Optional Param/ "resourceVersionMatch" - resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset
req `addQuery` toQuery ("resourceVersionMatch", Just xs)
587
+
578
588
--| /Optional Param/ "timeoutSeconds" - Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
@@ -616,6 +626,11 @@ instance HasOptionalParam ListNamespacedCustomObject Pretty where
616
626
applyOptionalParam req (Pretty xs) =
617
627
req `addQuery` toQuery ("pretty", Just xs)
618
628
629
+
--| /Optional Param/ "allowWatchBookmarks" - 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.
req `addQuery` toQuery ("allowWatchBookmarks", Just xs)
633
+
619
634
-- | /Optional Param/ "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.
@@ -641,6 +656,11 @@ instance HasOptionalParam ListNamespacedCustomObject ResourceVersion where
641
656
applyOptionalParam req (ResourceVersion xs) =
642
657
req `addQuery` toQuery ("resourceVersion", Just xs)
643
658
659
+
--| /Optional Param/ "resourceVersionMatch" - resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset
req `addQuery` toQuery ("resourceVersionMatch", Just xs)
663
+
644
664
--| /Optional Param/ "timeoutSeconds" - Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity.
Copy file name to clipboardExpand all lines: kubernetes/openapi.yaml
+38Lines changed: 38 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -68576,6 +68576,17 @@ paths:
68576
68576
required: true
68577
68577
schema:
68578
68578
type: string
68579
+
- description: allowWatchBookmarks requests watch events with type "BOOKMARK".
68580
+
Servers that do not implement bookmarks may ignore this flag and bookmarks
68581
+
are sent at the server's discretion. Clients should not assume bookmarks
68582
+
are returned at any specific interval, nor may they assume the server will
68583
+
send any BOOKMARK event during a session. If this is not a watch, this field
68584
+
is ignored. If the feature gate WatchBookmarks is not enabled in apiserver,
68585
+
this field is ignored.
68586
+
in: query
68587
+
name: allowWatchBookmarks
68588
+
schema:
68589
+
type: boolean
68579
68590
- description: |-
68580
68591
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".
68581
68592
@@ -68614,6 +68625,14 @@ paths:
68614
68625
name: resourceVersion
68615
68626
schema:
68616
68627
type: string
68628
+
- description: |-
68629
+
resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.
68630
+
68631
+
Defaults to unset
68632
+
in: query
68633
+
name: resourceVersionMatch
68634
+
schema:
68635
+
type: string
68617
68636
- description: Timeout for the list/watch call. This limits the duration of
68618
68637
the call, regardless of any activity or inactivity.
68619
68638
in: query
@@ -68819,6 +68838,17 @@ paths:
68819
68838
required: true
68820
68839
schema:
68821
68840
type: string
68841
+
- description: allowWatchBookmarks requests watch events with type "BOOKMARK".
68842
+
Servers that do not implement bookmarks may ignore this flag and bookmarks
68843
+
are sent at the server's discretion. Clients should not assume bookmarks
68844
+
are returned at any specific interval, nor may they assume the server will
68845
+
send any BOOKMARK event during a session. If this is not a watch, this field
68846
+
is ignored. If the feature gate WatchBookmarks is not enabled in apiserver,
68847
+
this field is ignored.
68848
+
in: query
68849
+
name: allowWatchBookmarks
68850
+
schema:
68851
+
type: boolean
68822
68852
- description: |-
68823
68853
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".
68824
68854
@@ -68857,6 +68887,14 @@ paths:
68857
68887
name: resourceVersion
68858
68888
schema:
68859
68889
type: string
68890
+
- description: |-
68891
+
resourceVersionMatch determines how resourceVersion is applied to list calls. It is highly recommended that resourceVersionMatch be set for list calls where resourceVersion is set See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details.
68892
+
68893
+
Defaults to unset
68894
+
in: query
68895
+
name: resourceVersionMatch
68896
+
schema:
68897
+
type: string
68860
68898
- description: Timeout for the list/watch call. This limits the duration of
68861
68899
the call, regardless of any activity or inactivity.
0 commit comments