Class: Google::Apis::GenomicsV2alpha1::CheckInRequest
- Inherits:
-
Object
- Object
- Google::Apis::GenomicsV2alpha1::CheckInRequest
- Includes:
- Core::Hashable, Core::JsonObjectSupport
- Defined in:
- generated/google/apis/genomics_v2alpha1/classes.rb,
generated/google/apis/genomics_v2alpha1/representations.rb,
generated/google/apis/genomics_v2alpha1/representations.rb
Overview
The parameters to the CheckIn method.
Instance Attribute Summary collapse
-
#deadline_expired ⇒ Google::Apis::GenomicsV2alpha1::Empty
A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs.
-
#event ⇒ Hash<String,Object>
A workflow specific event occurred.
-
#result ⇒ Google::Apis::GenomicsV2alpha1::Status
The
Status
type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. -
#worker_status ⇒ Google::Apis::GenomicsV2alpha1::WorkerStatus
The status of the worker VM.
Instance Method Summary collapse
-
#initialize(**args) ⇒ CheckInRequest
constructor
A new instance of CheckInRequest.
-
#update!(**args) ⇒ Object
Update properties of this object.
Methods included from Core::JsonObjectSupport
Methods included from Core::Hashable
Constructor Details
#initialize(**args) ⇒ CheckInRequest
Returns a new instance of CheckInRequest
270 271 272 |
# File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 270 def initialize(**args) update!(**args) end |
Instance Attribute Details
#deadline_expired ⇒ Google::Apis::GenomicsV2alpha1::Empty
A generic empty message that you can re-use to avoid defining duplicated
empty messages in your APIs. A typical example is to use it as the request
or the response type of an API method. For instance:
service Foo
rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty);
The JSON representation for Empty
is empty JSON object ```.
Corresponds to the JSON property
deadlineExpired`
215 216 217 |
# File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 215 def deadline_expired @deadline_expired end |
#event ⇒ Hash<String,Object>
A workflow specific event occurred.
Corresponds to the JSON property event
220 221 222 |
# File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 220 def event @event end |
#result ⇒ Google::Apis::GenomicsV2alpha1::Status
The Status
type defines a logical error model that is suitable for different
programming environments, including REST APIs and RPC APIs. It is used by
gRPC. The error model is designed to be:
- Simple to use and understand for most users
- Flexible enough to meet unexpected needs
# Overview
The
Status
message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the packagegoogle.rpc
that can be used for common error conditions. # Language mapping TheStatus
message is the logical representation of the error model, but it is not necessarily the actual wire format. When theStatus
message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C. # Other uses The error model and theStatus
message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments. Example uses of this error model include: - Partial errors. If a service needs to return partial errors to the client,
it may embed the
Status
in the normal response to indicate the partial errors. - Workflow errors. A typical workflow has multiple steps. Each step may
have a
Status
message for error reporting. - Batch operations. If a client uses batch request and batch response, the
Status
message should be used directly inside batch response, one for each error sub-response. - Asynchronous operations. If an API call embeds asynchronous operation
results in its response, the status of those operations should be
represented directly using the
Status
message. - Logging. If some API errors are stored in logs, the message
Status
could be used directly after any stripping needed for security/privacy reasons. Corresponds to the JSON propertyresult
263 264 265 |
# File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 263 def result @result end |
#worker_status ⇒ Google::Apis::GenomicsV2alpha1::WorkerStatus
The status of the worker VM.
Corresponds to the JSON property workerStatus
268 269 270 |
# File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 268 def worker_status @worker_status end |
Instance Method Details
#update!(**args) ⇒ Object
Update properties of this object
275 276 277 278 279 280 |
# File 'generated/google/apis/genomics_v2alpha1/classes.rb', line 275 def update!(**args) @deadline_expired = args[:deadline_expired] if args.key?(:deadline_expired) @event = args[:event] if args.key?(:event) @result = args[:result] if args.key?(:result) @worker_status = args[:worker_status] if args.key?(:worker_status) end |