ArgoWorkflows::EventSourceServiceApi
All URIs are relative to http://localhost:2746
| Method | HTTP request | Description |
|---|---|---|
| event_source_service_create_event_source | POST /api/v1/event-sources/namespace | |
| event_source_service_delete_event_source | DELETE /api/v1/event-sources/namespace/name | |
| event_source_service_event_sources_logs | GET /api/v1/stream/event-sources/namespace/logs | |
| event_source_service_get_event_source | GET /api/v1/event-sources/namespace/name | |
| event_source_service_list_event_sources | GET /api/v1/event-sources/namespace | |
| event_source_service_update_event_source | PUT /api/v1/event-sources/namespace/name | |
| event_source_service_watch_event_sources | GET /api/v1/stream/event-sources/namespace |
event_source_service_create_event_source
IoArgoprojEventsV1alpha1EventSource event_source_service_create_event_source(namespace, body)
Example
# load the gem
require 'argo_workflows'
# setup authorization
ArgoWorkflows.configure do |config|
# Configure API key authorization: BearerToken
config.api_key['Authorization'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
#config.api_key_prefix['Authorization'] = 'Bearer'
end
api_instance = ArgoWorkflows::EventSourceServiceApi.new
namespace = 'namespace_example' # String |
body = ArgoWorkflows::EventsourceCreateEventSourceRequest.new # EventsourceCreateEventSourceRequest |
begin
result = api_instance.event_source_service_create_event_source(namespace, body)
p result
rescue ArgoWorkflows::ApiError => e
puts "Exception when calling EventSourceServiceApi->event_source_service_create_event_source: #{e}"
end
Parameters
| Name | Type | Description | Notes |
|---|---|---|---|
| namespace | String | ||
| body | EventsourceCreateEventSourceRequest |
Return type
IoArgoprojEventsV1alpha1EventSource
Authorization
HTTP request headers
- Content-Type: application/json
- Accept: application/json
event_source_service_delete_event_source
EventsourceEventSourceDeletedResponse event_source_service_delete_event_source(namespace, name, opts)
Example
# load the gem
require 'argo_workflows'
# setup authorization
ArgoWorkflows.configure do |config|
# Configure API key authorization: BearerToken
config.api_key['Authorization'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
#config.api_key_prefix['Authorization'] = 'Bearer'
end
api_instance = ArgoWorkflows::EventSourceServiceApi.new
namespace = 'namespace_example' # String |
name = 'name_example' # String |
opts = {
delete_options_grace_period_seconds: 'delete_options_grace_period_seconds_example', # String | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately. +optional.
delete_options_preconditions_uid: 'delete_options_preconditions_uid_example', # String | Specifies the target UID. +optional.
delete_options_preconditions_resource_version: 'delete_options_preconditions_resource_version_example', # String | Specifies the target ResourceVersion +optional.
delete_options_orphan_dependents: true, # BOOLEAN | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the \"orphan\" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both. +optional.
delete_options_propagation_policy: 'delete_options_propagation_policy_example', # String | Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. +optional.
delete_options_dry_run: ['delete_options_dry_run_example'] # Array<String> | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed +optional +listType=atomic.
}
begin
result = api_instance.event_source_service_delete_event_source(namespace, name, opts)
p result
rescue ArgoWorkflows::ApiError => e
puts "Exception when calling EventSourceServiceApi->event_source_service_delete_event_source: #{e}"
end
Parameters
| Name | Type | Description | Notes |
|---|---|---|---|
| namespace | String | ||
| name | String | ||
| delete_options_grace_period_seconds | String | The duration in seconds before the object should be deleted. Value must be non-negative integer. The value zero indicates delete immediately. If this value is nil, the default grace period for the specified type will be used. Defaults to a per object value if not specified. zero means delete immediately. +optional. | [optional] |
| delete_options_preconditions_uid | String | Specifies the target UID. +optional. | [optional] |
| delete_options_preconditions_resource_version | String | Specifies the target ResourceVersion +optional. | [optional] |
| delete_options_orphan_dependents | BOOLEAN | Deprecated: please use the PropagationPolicy, this field will be deprecated in 1.7. Should the dependent objects be orphaned. If true/false, the "orphan" finalizer will be added to/removed from the object's finalizers list. Either this field or PropagationPolicy may be set, but not both. +optional. | [optional] |
| delete_options_propagation_policy | String | Whether and how garbage collection will be performed. Either this field or OrphanDependents may be set, but not both. The default policy is decided by the existing finalizer set in the metadata.finalizers and the resource-specific default policy. Acceptable values are: 'Orphan' - orphan the dependents; 'Background' - allow the garbage collector to delete the dependents in the background; 'Foreground' - a cascading policy that deletes all dependents in the foreground. +optional. | [optional] |
| delete_options_dry_run | Array<String> | When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed +optional +listType=atomic. | [optional] |
Return type
EventsourceEventSourceDeletedResponse
Authorization
HTTP request headers
- Content-Type: application/json
- Accept: application/json
event_source_service_event_sources_logs
StreamResultOfEventsourceLogEntry event_source_service_event_sources_logs(namespace, opts)
Example
# load the gem
require 'argo_workflows'
# setup authorization
ArgoWorkflows.configure do |config|
# Configure API key authorization: BearerToken
config.api_key['Authorization'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
#config.api_key_prefix['Authorization'] = 'Bearer'
end
api_instance = ArgoWorkflows::EventSourceServiceApi.new
namespace = 'namespace_example' # String |
opts = {
name: 'name_example', # String | optional - only return entries for this event source.
event_source_type: 'event_source_type_example', # String | optional - only return entries for this event source type (e.g. `webhook`).
event_name: 'event_name_example', # String | optional - only return entries for this event name (e.g. `example`).
grep: 'grep_example', # String | optional - only return entries where `msg` matches this regular expression.
pod_log_options_container: 'pod_log_options_container_example', # String | The container for which to stream logs. Defaults to only container if there is one container in the pod. +optional.
pod_log_options_follow: true, # BOOLEAN | Follow the log stream of the pod. Defaults to false. +optional.
pod_log_options_previous: true, # BOOLEAN | Return previous terminated container logs. Defaults to false. +optional.
pod_log_options_since_seconds: 'pod_log_options_since_seconds_example', # String | A relative time in seconds before the current time from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified. +optional.
pod_log_options_since_time_seconds: 'pod_log_options_since_time_seconds_example', # String | Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive.
pod_log_options_since_time_nanos: 56, # Integer | Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive. This field may be limited in precision depending on context.
pod_log_options_timestamps: true, # BOOLEAN | If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false. +optional.
pod_log_options_tail_lines: 'pod_log_options_tail_lines_example', # String | If set, the number of lines from the end of the logs to show. If not specified, logs are shown from the creation of the container or sinceSeconds or sinceTime +optional.
pod_log_options_limit_bytes: 'pod_log_options_limit_bytes_example', # String | If set, the number of bytes to read from the server before terminating the log output. This may not display a complete final line of logging, and may return slightly more or slightly less than the specified limit. +optional.
pod_log_options_insecure_skip_tls_verify_backend: true # BOOLEAN | insecureSkipTLSVerifyBackend indicates that the apiserver should not confirm the validity of the serving certificate of the backend it is connecting to. This will make the HTTPS connection between the apiserver and the backend insecure. This means the apiserver cannot verify the log data it is receiving came from the real kubelet. If the kubelet is configured to verify the apiserver's TLS credentials, it does not mean the connection to the real kubelet is vulnerable to a man in the middle attack (e.g. an attacker could not intercept the actual log data coming from the real kubelet). +optional.
}
begin
result = api_instance.event_source_service_event_sources_logs(namespace, opts)
p result
rescue ArgoWorkflows::ApiError => e
puts "Exception when calling EventSourceServiceApi->event_source_service_event_sources_logs: #{e}"
end
Parameters
| Name | Type | Description | Notes |
|---|---|---|---|
| namespace | String | ||
| name | String | optional - only return entries for this event source. | [optional] |
| event_source_type | String | optional - only return entries for this event source type (e.g. `webhook`). | [optional] |
| event_name | String | optional - only return entries for this event name (e.g. `example`). | [optional] |
| grep | String | optional - only return entries where `msg` matches this regular expression. | [optional] |
| pod_log_options_container | String | The container for which to stream logs. Defaults to only container if there is one container in the pod. +optional. | [optional] |
| pod_log_options_follow | BOOLEAN | Follow the log stream of the pod. Defaults to false. +optional. | [optional] |
| pod_log_options_previous | BOOLEAN | Return previous terminated container logs. Defaults to false. +optional. | [optional] |
| pod_log_options_since_seconds | String | A relative time in seconds before the current time from which to show logs. If this value precedes the time a pod was started, only logs since the pod start will be returned. If this value is in the future, no logs will be returned. Only one of sinceSeconds or sinceTime may be specified. +optional. | [optional] |
| pod_log_options_since_time_seconds | String | Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive. | [optional] |
| pod_log_options_since_time_nanos | Integer | Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive. This field may be limited in precision depending on context. | [optional] |
| pod_log_options_timestamps | BOOLEAN | If true, add an RFC3339 or RFC3339Nano timestamp at the beginning of every line of log output. Defaults to false. +optional. | [optional] |
| pod_log_options_tail_lines | String | If set, the number of lines from the end of the logs to show. If not specified, logs are shown from the creation of the container or sinceSeconds or sinceTime +optional. | [optional] |
| pod_log_options_limit_bytes | String | If set, the number of bytes to read from the server before terminating the log output. This may not display a complete final line of logging, and may return slightly more or slightly less than the specified limit. +optional. | [optional] |
| pod_log_options_insecure_skip_tls_verify_backend | BOOLEAN | insecureSkipTLSVerifyBackend indicates that the apiserver should not confirm the validity of the serving certificate of the backend it is connecting to. This will make the HTTPS connection between the apiserver and the backend insecure. This means the apiserver cannot verify the log data it is receiving came from the real kubelet. If the kubelet is configured to verify the apiserver's TLS credentials, it does not mean the connection to the real kubelet is vulnerable to a man in the middle attack (e.g. an attacker could not intercept the actual log data coming from the real kubelet). +optional. | [optional] |
Return type
StreamResultOfEventsourceLogEntry
Authorization
HTTP request headers
- Content-Type: application/json
- Accept: application/json
event_source_service_get_event_source
IoArgoprojEventsV1alpha1EventSource event_source_service_get_event_source(namespace, name)
Example
# load the gem
require 'argo_workflows'
# setup authorization
ArgoWorkflows.configure do |config|
# Configure API key authorization: BearerToken
config.api_key['Authorization'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
#config.api_key_prefix['Authorization'] = 'Bearer'
end
api_instance = ArgoWorkflows::EventSourceServiceApi.new
namespace = 'namespace_example' # String |
name = 'name_example' # String |
begin
result = api_instance.event_source_service_get_event_source(namespace, name)
p result
rescue ArgoWorkflows::ApiError => e
puts "Exception when calling EventSourceServiceApi->event_source_service_get_event_source: #{e}"
end
Parameters
| Name | Type | Description | Notes |
|---|---|---|---|
| namespace | String | ||
| name | String |
Return type
IoArgoprojEventsV1alpha1EventSource
Authorization
HTTP request headers
- Content-Type: application/json
- Accept: application/json
event_source_service_list_event_sources
IoArgoprojEventsV1alpha1EventSourceList event_source_service_list_event_sources(namespace, opts)
Example
# load the gem
require 'argo_workflows'
# setup authorization
ArgoWorkflows.configure do |config|
# Configure API key authorization: BearerToken
config.api_key['Authorization'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
#config.api_key_prefix['Authorization'] = 'Bearer'
end
api_instance = ArgoWorkflows::EventSourceServiceApi.new
namespace = 'namespace_example' # String |
opts = {
list_options_label_selector: 'list_options_label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything. +optional.
list_options_field_selector: 'list_options_field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything. +optional.
list_options_watch: true, # BOOLEAN | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. +optional.
list_options_allow_watch_bookmarks: true, # BOOLEAN | 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. +optional.
list_options_resource_version: 'list_options_resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset +optional
list_options_resource_version_match: 'list_options_resource_version_match_example', # String | 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 +optional
list_options_timeout_seconds: 'list_options_timeout_seconds_example', # String | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. +optional.
list_options_limit: 'list_options_limit_example', # String | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
list_options_continue: 'list_options_continue_example', # String | 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.
list_options_send_initial_events: true # BOOLEAN | `sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"io.k8s.initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as \"data at least as new as the provided `resourceVersion`\" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise. +optional
}
begin
result = api_instance.event_source_service_list_event_sources(namespace, opts)
p result
rescue ArgoWorkflows::ApiError => e
puts "Exception when calling EventSourceServiceApi->event_source_service_list_event_sources: #{e}"
end
Parameters
| Name | Type | Description | Notes |
|---|---|---|---|
| namespace | String | ||
| list_options_label_selector | String | A selector to restrict the list of returned objects by their labels. Defaults to everything. +optional. | [optional] |
| list_options_field_selector | String | A selector to restrict the list of returned objects by their fields. Defaults to everything. +optional. | [optional] |
| list_options_watch | BOOLEAN | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. +optional. | [optional] |
| list_options_allow_watch_bookmarks | BOOLEAN | 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. +optional. | [optional] |
| list_options_resource_version | String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset +optional | [optional] |
| list_options_resource_version_match | String | 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 +optional | [optional] |
| list_options_timeout_seconds | String | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. +optional. | [optional] |
| list_options_limit | String | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
| list_options_continue | String | 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. | [optional] |
| list_options_send_initial_events | BOOLEAN | `sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"io.k8s.initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise. +optional | [optional] |
Return type
IoArgoprojEventsV1alpha1EventSourceList
Authorization
HTTP request headers
- Content-Type: application/json
- Accept: application/json
event_source_service_update_event_source
IoArgoprojEventsV1alpha1EventSource event_source_service_update_event_source(namespace, name, body)
Example
# load the gem
require 'argo_workflows'
# setup authorization
ArgoWorkflows.configure do |config|
# Configure API key authorization: BearerToken
config.api_key['Authorization'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
#config.api_key_prefix['Authorization'] = 'Bearer'
end
api_instance = ArgoWorkflows::EventSourceServiceApi.new
namespace = 'namespace_example' # String |
name = 'name_example' # String |
body = ArgoWorkflows::EventsourceUpdateEventSourceRequest.new # EventsourceUpdateEventSourceRequest |
begin
result = api_instance.event_source_service_update_event_source(namespace, name, body)
p result
rescue ArgoWorkflows::ApiError => e
puts "Exception when calling EventSourceServiceApi->event_source_service_update_event_source: #{e}"
end
Parameters
| Name | Type | Description | Notes |
|---|---|---|---|
| namespace | String | ||
| name | String | ||
| body | EventsourceUpdateEventSourceRequest |
Return type
IoArgoprojEventsV1alpha1EventSource
Authorization
HTTP request headers
- Content-Type: application/json
- Accept: application/json
event_source_service_watch_event_sources
StreamResultOfEventsourceEventSourceWatchEvent event_source_service_watch_event_sources(namespace, opts)
Example
# load the gem
require 'argo_workflows'
# setup authorization
ArgoWorkflows.configure do |config|
# Configure API key authorization: BearerToken
config.api_key['Authorization'] = 'YOUR API KEY'
# Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
#config.api_key_prefix['Authorization'] = 'Bearer'
end
api_instance = ArgoWorkflows::EventSourceServiceApi.new
namespace = 'namespace_example' # String |
opts = {
list_options_label_selector: 'list_options_label_selector_example', # String | A selector to restrict the list of returned objects by their labels. Defaults to everything. +optional.
list_options_field_selector: 'list_options_field_selector_example', # String | A selector to restrict the list of returned objects by their fields. Defaults to everything. +optional.
list_options_watch: true, # BOOLEAN | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. +optional.
list_options_allow_watch_bookmarks: true, # BOOLEAN | 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. +optional.
list_options_resource_version: 'list_options_resource_version_example', # String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset +optional
list_options_resource_version_match: 'list_options_resource_version_match_example', # String | 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 +optional
list_options_timeout_seconds: 'list_options_timeout_seconds_example', # String | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. +optional.
list_options_limit: 'list_options_limit_example', # String | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned.
list_options_continue: 'list_options_continue_example', # String | 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.
list_options_send_initial_events: true # BOOLEAN | `sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic \"Bookmark\" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `\"io.k8s.initial-events-end\": \"true\"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as \"data at least as new as the provided `resourceVersion`\" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as \"consistent read\" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=\"\"` or `resourceVersion=\"0\"` (for backward compatibility reasons) and to false otherwise. +optional
}
begin
result = api_instance.event_source_service_watch_event_sources(namespace, opts)
p result
rescue ArgoWorkflows::ApiError => e
puts "Exception when calling EventSourceServiceApi->event_source_service_watch_event_sources: #{e}"
end
Parameters
| Name | Type | Description | Notes |
|---|---|---|---|
| namespace | String | ||
| list_options_label_selector | String | A selector to restrict the list of returned objects by their labels. Defaults to everything. +optional. | [optional] |
| list_options_field_selector | String | A selector to restrict the list of returned objects by their fields. Defaults to everything. +optional. | [optional] |
| list_options_watch | BOOLEAN | Watch for changes to the described resources and return them as a stream of add, update, and remove notifications. Specify resourceVersion. +optional. | [optional] |
| list_options_allow_watch_bookmarks | BOOLEAN | 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. +optional. | [optional] |
| list_options_resource_version | String | resourceVersion sets a constraint on what resource versions a request may be served from. See https://kubernetes.io/docs/reference/using-api/api-concepts/#resource-versions for details. Defaults to unset +optional | [optional] |
| list_options_resource_version_match | String | 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 +optional | [optional] |
| list_options_timeout_seconds | String | Timeout for the list/watch call. This limits the duration of the call, regardless of any activity or inactivity. +optional. | [optional] |
| list_options_limit | String | limit is a maximum number of responses to return for a list call. If more items exist, the server will set the `continue` field on the list metadata to a value that can be used with the same initial query to retrieve the next set of results. Setting a limit may return fewer than the requested amount of items (up to zero items) in the event all requested objects are filtered out and clients should only use the presence of the continue field to determine whether more results are available. Servers may choose not to support the limit argument and will return all of the available results. If limit is specified and the continue field is empty, clients may assume that no more results are available. This field is not supported if watch is true. The server guarantees that the objects returned when using continue will be identical to issuing a single list call without a limit - that is, no objects created, modified, or deleted after the first request is issued will be included in any subsequent continued requests. This is sometimes referred to as a consistent snapshot, and ensures that a client that is using limit to receive smaller chunks of a very large result can ensure they see all possible objects. If objects are updated during a chunked list the version of the object that was present at the time the first list result was calculated is returned. | [optional] |
| list_options_continue | String | 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. | [optional] |
| list_options_send_initial_events | BOOLEAN | `sendInitialEvents=true` may be set together with `watch=true`. In that case, the watch stream will begin with synthetic events to produce the current state of objects in the collection. Once all such events have been sent, a synthetic "Bookmark" event will be sent. The bookmark will report the ResourceVersion (RV) corresponding to the set of objects, and be marked with `"io.k8s.initial-events-end": "true"` annotation. Afterwards, the watch stream will proceed as usual, sending watch events corresponding to changes (subsequent to the RV) to objects watched. When `sendInitialEvents` option is set, we require `resourceVersionMatch` option to also be set. The semantic of the watch request is as following: - `resourceVersionMatch` = NotOlderThan is interpreted as "data at least as new as the provided `resourceVersion`" and the bookmark event is send when the state is synced to a `resourceVersion` at least as fresh as the one provided by the ListOptions. If `resourceVersion` is unset, this is interpreted as "consistent read" and the bookmark event is send when the state is synced at least to the moment when request started being processed. - `resourceVersionMatch` set to any other value or unset Invalid error is returned. Defaults to true if `resourceVersion=""` or `resourceVersion="0"` (for backward compatibility reasons) and to false otherwise. +optional | [optional] |
Return type
StreamResultOfEventsourceEventSourceWatchEvent
Authorization
HTTP request headers
- Content-Type: application/json
- Accept: application/json