google-api-client 0.27.3 → 0.28.0

data/generated/google/apis/logging_v2beta1/representations.rb

@@ -374,12 +374,14 @@ module Google
         class Representation < Google::Apis::Core::JsonRepresentation
           property :bucket_options, as: 'bucketOptions', class: Google::Apis::LoggingV2beta1::BucketOptions, decorator: Google::Apis::LoggingV2beta1::BucketOptions::Representation
       
+          property :create_time, as: 'createTime'
           property :description, as: 'description'
           property :filter, as: 'filter'
           hash :label_extractors, as: 'labelExtractors'
           property :metric_descriptor, as: 'metricDescriptor', class: Google::Apis::LoggingV2beta1::MetricDescriptor, decorator: Google::Apis::LoggingV2beta1::MetricDescriptor::Representation
       
           property :name, as: 'name'
+          property :update_time, as: 'updateTime'
           property :value_extractor, as: 'valueExtractor'
           property :version, as: 'version'
         end
@@ -388,11 +390,13 @@ module Google
       class LogSink
         # @private
         class Representation < Google::Apis::Core::JsonRepresentation
+          property :create_time, as: 'createTime'
           property :destination, as: 'destination'
           property :filter, as: 'filter'
           property :include_children, as: 'includeChildren'
           property :name, as: 'name'
           property :output_version_format, as: 'outputVersionFormat'
+          property :update_time, as: 'updateTime'
           property :writer_identity, as: 'writerIdentity'
         end
       end

data/generated/google/apis/logging_v2beta1/service.rb

@@ -497,7 +497,7 @@ module Google
         end
         
         # Updates a sink. This method replaces the following fields in the existing sink
-        # with values from the new sink: destination, and filter. The updated sink might
+        # with values from the new sink: destination, and filter.The updated sink might
         # also have a new writer_identity; see the unique_writer_identity field.
         # @param [String] sink_name
         #   Required. The full resource name of the sink to update, including the parent

data/generated/google/apis/ml_v1.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://cloud.google.com/ml/
     module MlV1
       VERSION = 'V1'
-      REVISION = '20181207'
+      REVISION = '20190115'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

data/generated/google/apis/ml_v1/classes.rb

@@ -53,12 +53,12 @@ module Google
       class GoogleApiHttpBody
         include Google::Apis::Core::Hashable
       
-        # The HTTP Content-Type string representing the content type of the body.
+        # The HTTP Content-Type header value specifying the content type of the body.
         # Corresponds to the JSON property `contentType`
         # @return [String]
         attr_accessor :content_type
       
-        # HTTP body binary data.
+        # The HTTP request/response body as raw binary.
         # Corresponds to the JSON property `data`
         # NOTE: Values are automatically base64 encoded/decoded in the client library.
         # @return [String]
@@ -445,7 +445,7 @@ module Google
         # @return [Hash<String,String>]
         attr_accessor :labels
       
-        # Represents input parameters for a prediction job. Next field: 20
+        # Represents input parameters for a prediction job.
         # Corresponds to the JSON property `predictionInput`
         # @return [Google::Apis::MlV1::GoogleCloudMlV1PredictionInput]
         attr_accessor :prediction_input
@@ -927,7 +927,7 @@ module Google
         end
       end
       
-      # Represents input parameters for a prediction job. Next field: 20
+      # Represents input parameters for a prediction job.
       class GoogleCloudMlV1PredictionInput
         include Google::Apis::Core::Hashable
       
@@ -1181,26 +1181,22 @@ module Google
         # <dt>standard_v100</dt>
         # <dd>
         # A machine equivalent to <i>standard</i> that
-        # also includes a single NVIDIA Tesla V100 GPU. The availability of these
-        # GPUs is in the <i>Beta</i> launch stage.
+        # also includes a single NVIDIA Tesla V100 GPU.
         # </dd>
         # <dt>large_model_v100</dt>
         # <dd>
         # A machine equivalent to <i>large_model</i> that
-        # also includes a single NVIDIA Tesla V100 GPU. The availability of these
-        # GPUs is in the <i>Beta</i> launch stage.
+        # also includes a single NVIDIA Tesla V100 GPU.
         # </dd>
         # <dt>complex_model_m_v100</dt>
         # <dd>
         # A machine equivalent to <i>complex_model_m</i> that
-        # also includes four NVIDIA Tesla V100 GPUs. The availability of these
-        # GPUs is in the <i>Beta</i> launch stage.
+        # also includes four NVIDIA Tesla V100 GPUs.
         # </dd>
         # <dt>complex_model_l_v100</dt>
         # <dd>
         # A machine equivalent to <i>complex_model_l</i> that
-        # also includes eight NVIDIA Tesla V100 GPUs. The availability of these
-        # GPUs is in the <i>Beta</i> launch stage.
+        # also includes eight NVIDIA Tesla V100 GPUs.
         # </dd>
         # <dt>cloud_tpu</dt>
         # <dd>
@@ -1226,6 +1222,7 @@ module Google
         # `parameter_server_type`.
         # This value can only be used when `scale_tier` is set to `CUSTOM`.If you
         # set this value, you must also set `parameter_server_type`.
+        # The default value is zero.
         # Corresponds to the JSON property `parameterServerCount`
         # @return [Fixnum]
         attr_accessor :parameter_server_count
@@ -1280,6 +1277,7 @@ module Google
         # replica in the cluster will be of the type specified in `worker_type`.
         # This value can only be used when `scale_tier` is set to `CUSTOM`. If you
         # set this value, you must also set `worker_type`.
+        # The default value is zero.
         # Corresponds to the JSON property `workerCount`
         # @return [Fixnum]
         attr_accessor :worker_count

data/generated/google/apis/remotebuildexecution_v1.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://cloud.google.com/remote-build-execution/docs/
     module RemotebuildexecutionV1
       VERSION = 'V1'
-      REVISION = '20190103'
+      REVISION = '20190116'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

data/generated/google/apis/remotebuildexecution_v1/classes.rb

@@ -63,11 +63,11 @@ module Google
         # When a `Digest` is used to refer to a proto message, it always refers to the
         # message in binary encoded form. To ensure consistent hashing, clients and
         # servers MUST ensure that they serialize messages according to the following
-        # rules, even if there are alternate valid encodings for the same message.
-        # - Fields are serialized in tag order.
-        # - There are no unknown fields.
-        # - There are no duplicate fields.
-        # - Fields are serialized according to the default semantics for their type.
+        # rules, even if there are alternate valid encodings for the same message:
+        # * Fields are serialized in tag order.
+        # * There are no unknown fields.
+        # * There are no duplicate fields.
+        # * Fields are serialized according to the default semantics for their type.
         # Most protocol buffer implementations will always follow these rules when
         # serializing, but care should be taken to avoid shortcuts. For instance,
         # concatenating two messages to merge them may produce duplicate fields.
@@ -100,11 +100,11 @@ module Google
         # When a `Digest` is used to refer to a proto message, it always refers to the
         # message in binary encoded form. To ensure consistent hashing, clients and
         # servers MUST ensure that they serialize messages according to the following
-        # rules, even if there are alternate valid encodings for the same message.
-        # - Fields are serialized in tag order.
-        # - There are no unknown fields.
-        # - There are no duplicate fields.
-        # - Fields are serialized according to the default semantics for their type.
+        # rules, even if there are alternate valid encodings for the same message:
+        # * Fields are serialized in tag order.
+        # * There are no unknown fields.
+        # * There are no duplicate fields.
+        # * Fields are serialized according to the default semantics for their type.
         # Most protocol buffer implementations will always follow these rules when
         # serializing, but care should be taken to avoid shortcuts. For instance,
         # concatenating two messages to merge them may produce duplicate fields.
@@ -285,11 +285,11 @@ module Google
         # When a `Digest` is used to refer to a proto message, it always refers to the
         # message in binary encoded form. To ensure consistent hashing, clients and
         # servers MUST ensure that they serialize messages according to the following
-        # rules, even if there are alternate valid encodings for the same message.
-        # - Fields are serialized in tag order.
-        # - There are no unknown fields.
-        # - There are no duplicate fields.
-        # - Fields are serialized according to the default semantics for their type.
+        # rules, even if there are alternate valid encodings for the same message:
+        # * Fields are serialized in tag order.
+        # * There are no unknown fields.
+        # * There are no duplicate fields.
+        # * Fields are serialized according to the default semantics for their type.
         # Most protocol buffer implementations will always follow these rules when
         # serializing, but care should be taken to avoid shortcuts. For instance,
         # concatenating two messages to merge them may produce duplicate fields.
@@ -327,11 +327,11 @@ module Google
         # When a `Digest` is used to refer to a proto message, it always refers to the
         # message in binary encoded form. To ensure consistent hashing, clients and
         # servers MUST ensure that they serialize messages according to the following
-        # rules, even if there are alternate valid encodings for the same message.
-        # - Fields are serialized in tag order.
-        # - There are no unknown fields.
-        # - There are no duplicate fields.
-        # - Fields are serialized according to the default semantics for their type.
+        # rules, even if there are alternate valid encodings for the same message:
+        # * Fields are serialized in tag order.
+        # * There are no unknown fields.
+        # * There are no duplicate fields.
+        # * Fields are serialized according to the default semantics for their type.
         # Most protocol buffer implementations will always follow these rules when
         # serializing, but care should be taken to avoid shortcuts. For instance,
         # concatenating two messages to merge them may produce duplicate fields.
@@ -388,7 +388,8 @@ module Google
         # The environment variables to set when running the program. The worker may
         # provide its own default environment variables; these defaults can be
         # overridden using this field. Additional variables can also be specified.
-        # In order to ensure that equivalent `Command`s always hash to the same
+        # In order to ensure that equivalent
+        # Commands always hash to the same
         # value, the environment variables MUST be lexicographically sorted by name.
         # Sorting of strings is done by code point, equivalently, by the UTF-8 bytes.
         # Corresponds to the JSON property `environmentVariables`
@@ -396,10 +397,12 @@ module Google
         attr_accessor :environment_variables
       
         # A list of the output directories that the client expects to retrieve from
-        # the action. Only the contents of the indicated directories (recursively
-        # including the contents of their subdirectories) will be
-        # returned, as well as files listed in `output_files`. Other files that may
-        # be created during command execution are discarded.
+        # the action. Only the listed directories will be returned (an entire
+        # directory structure will be returned as a
+        # Tree message digest, see
+        # OutputDirectory), as
+        # well as files listed in `output_files`. Other files or directories that
+        # may be created during command execution are discarded.
         # The paths are relative to the working directory of the action execution.
         # The paths are specified using a single forward slash (`/`) as a path
         # separator, even if the execution platform natively uses a different
@@ -410,9 +413,11 @@ module Google
         # In order to ensure consistent hashing of the same Action, the output paths
         # MUST be sorted lexicographically by code point (or, equivalently, by UTF-8
         # bytes).
-        # An output directory cannot be duplicated, be a parent of another output
-        # directory, be a parent of a listed output file, or have the same path as
-        # any of the listed output files.
+        # An output directory cannot be duplicated or have the same path as any of
+        # the listed output files.
+        # Directories leading up to the output directories (but not the output
+        # directories themselves) are created by the worker prior to execution, even
+        # if they are not explicitly part of the input root.
         # Corresponds to the JSON property `outputDirectories`
         # @return [Array<String>]
         attr_accessor :output_directories
@@ -420,7 +425,8 @@ module Google
         # A list of the output files that the client expects to retrieve from the
         # action. Only the listed files, as well as directories listed in
         # `output_directories`, will be returned to the client as output.
-        # Other files that may be created during command execution are discarded.
+        # Other files or directories that may be created during command execution
+        # are discarded.
         # The paths are relative to the working directory of the action execution.
         # The paths are specified using a single forward slash (`/`) as a path
         # separator, even if the execution platform natively uses a different
@@ -429,9 +435,10 @@ module Google
         # In order to ensure consistent hashing of the same Action, the output paths
         # MUST be sorted lexicographically by code point (or, equivalently, by UTF-8
         # bytes).
-        # An output file cannot be duplicated, be a parent of another output file, be
-        # a child of a listed output directory, or have the same path as any of the
-        # listed output directories.
+        # An output file cannot be duplicated, be a parent of another output file, or
+        # have the same path as any of the listed output directories.
+        # Directories leading up to the output files are created by the worker prior
+        # to execution, even if they are not explicitly part of the input root.
         # Corresponds to the JSON property `outputFiles`
         # @return [Array<String>]
         attr_accessor :output_files
@@ -512,11 +519,11 @@ module Google
       # When a `Digest` is used to refer to a proto message, it always refers to the
       # message in binary encoded form. To ensure consistent hashing, clients and
       # servers MUST ensure that they serialize messages according to the following
-      # rules, even if there are alternate valid encodings for the same message.
-      # - Fields are serialized in tag order.
-      # - There are no unknown fields.
-      # - There are no duplicate fields.
-      # - Fields are serialized according to the default semantics for their type.
+      # rules, even if there are alternate valid encodings for the same message:
+      # * Fields are serialized in tag order.
+      # * There are no unknown fields.
+      # * There are no duplicate fields.
+      # * Fields are serialized according to the default semantics for their type.
       # Most protocol buffer implementations will always follow these rules when
       # serializing, but care should be taken to avoid shortcuts. For instance,
       # concatenating two messages to merge them may produce duplicate fields.
@@ -555,10 +562,10 @@ module Google
       # In order to ensure that two equivalent directory trees hash to the same
       # value, the following restrictions MUST be obeyed when constructing a
       # a `Directory`:
-      # - Every child in the directory must have a path of exactly one segment.
+      # * Every child in the directory must have a path of exactly one segment.
       # Multiple levels of directory hierarchy may not be collapsed.
-      # - Each child in the directory must have a unique path segment (file name).
-      # - The files, directories and symlinks in the directory must each be sorted
+      # * Each child in the directory must have a unique path segment (file name).
+      # * The files, directories and symlinks in the directory must each be sorted
       # in lexicographical order by path. The path strings must be sorted by code
       # point, equivalently, by UTF-8 bytes.
       # A `Directory` that obeys the restrictions is said to be in canonical form.
@@ -656,11 +663,11 @@ module Google
         # When a `Digest` is used to refer to a proto message, it always refers to the
         # message in binary encoded form. To ensure consistent hashing, clients and
         # servers MUST ensure that they serialize messages according to the following
-        # rules, even if there are alternate valid encodings for the same message.
-        # - Fields are serialized in tag order.
-        # - There are no unknown fields.
-        # - There are no duplicate fields.
-        # - Fields are serialized according to the default semantics for their type.
+        # rules, even if there are alternate valid encodings for the same message:
+        # * Fields are serialized in tag order.
+        # * There are no unknown fields.
+        # * There are no duplicate fields.
+        # * Fields are serialized according to the default semantics for their type.
         # Most protocol buffer implementations will always follow these rules when
         # serializing, but care should be taken to avoid shortcuts. For instance,
         # concatenating two messages to merge them may produce duplicate fields.
@@ -711,11 +718,11 @@ module Google
         # When a `Digest` is used to refer to a proto message, it always refers to the
         # message in binary encoded form. To ensure consistent hashing, clients and
         # servers MUST ensure that they serialize messages according to the following
-        # rules, even if there are alternate valid encodings for the same message.
-        # - Fields are serialized in tag order.
-        # - There are no unknown fields.
-        # - There are no duplicate fields.
-        # - Fields are serialized according to the default semantics for their type.
+        # rules, even if there are alternate valid encodings for the same message:
+        # * Fields are serialized in tag order.
+        # * There are no unknown fields.
+        # * There are no duplicate fields.
+        # * Fields are serialized according to the default semantics for their type.
         # Most protocol buffer implementations will always follow these rules when
         # serializing, but care should be taken to avoid shortcuts. For instance,
         # concatenating two messages to merge them may produce duplicate fields.
@@ -769,6 +776,12 @@ module Google
         attr_accessor :cached_result
         alias_method :cached_result?, :cached_result
       
+        # Freeform informational message with details on the execution of the action
+        # that may be displayed to the user upon failure or when requested explicitly.
+        # Corresponds to the JSON property `message`
+        # @return [String]
+        attr_accessor :message
+      
         # An ActionResult represents the result of an
         # Action being run.
         # Corresponds to the JSON property `result`
@@ -836,6 +849,7 @@ module Google
         # Update properties of this object
         def update!(**args)
           @cached_result = args[:cached_result] if args.key?(:cached_result)
+          @message = args[:message] if args.key?(:message)
           @result = args[:result] if args.key?(:result)
           @server_logs = args[:server_logs] if args.key?(:server_logs)
           @status = args[:status] if args.key?(:status)
@@ -938,11 +952,11 @@ module Google
         # When a `Digest` is used to refer to a proto message, it always refers to the
         # message in binary encoded form. To ensure consistent hashing, clients and
         # servers MUST ensure that they serialize messages according to the following
-        # rules, even if there are alternate valid encodings for the same message.
-        # - Fields are serialized in tag order.
-        # - There are no unknown fields.
-        # - There are no duplicate fields.
-        # - Fields are serialized according to the default semantics for their type.
+        # rules, even if there are alternate valid encodings for the same message:
+        # * Fields are serialized in tag order.
+        # * There are no unknown fields.
+        # * There are no duplicate fields.
+        # * Fields are serialized according to the default semantics for their type.
         # Most protocol buffer implementations will always follow these rules when
         # serializing, but care should be taken to avoid shortcuts. For instance,
         # concatenating two messages to merge them may produce duplicate fields.
@@ -996,11 +1010,11 @@ module Google
         # When a `Digest` is used to refer to a proto message, it always refers to the
         # message in binary encoded form. To ensure consistent hashing, clients and
         # servers MUST ensure that they serialize messages according to the following
-        # rules, even if there are alternate valid encodings for the same message.
-        # - Fields are serialized in tag order.
-        # - There are no unknown fields.
-        # - There are no duplicate fields.
-        # - Fields are serialized according to the default semantics for their type.
+        # rules, even if there are alternate valid encodings for the same message:
+        # * Fields are serialized in tag order.
+        # * There are no unknown fields.
+        # * There are no duplicate fields.
+        # * Fields are serialized according to the default semantics for their type.
         # Most protocol buffer implementations will always follow these rules when
         # serializing, but care should be taken to avoid shortcuts. For instance,
         # concatenating two messages to merge them may produce duplicate fields.
@@ -1061,11 +1075,11 @@ module Google
         # When a `Digest` is used to refer to a proto message, it always refers to the
         # message in binary encoded form. To ensure consistent hashing, clients and
         # servers MUST ensure that they serialize messages according to the following
-        # rules, even if there are alternate valid encodings for the same message.
-        # - Fields are serialized in tag order.
-        # - There are no unknown fields.
-        # - There are no duplicate fields.
-        # - Fields are serialized according to the default semantics for their type.
+        # rules, even if there are alternate valid encodings for the same message:
+        # * Fields are serialized in tag order.
+        # * There are no unknown fields.
+        # * There are no duplicate fields.
+        # * Fields are serialized according to the default semantics for their type.
         # Most protocol buffer implementations will always follow these rules when
         # serializing, but care should be taken to avoid shortcuts. For instance,
         # concatenating two messages to merge them may produce duplicate fields.
@@ -1111,11 +1125,11 @@ module Google
         # When a `Digest` is used to refer to a proto message, it always refers to the
         # message in binary encoded form. To ensure consistent hashing, clients and
         # servers MUST ensure that they serialize messages according to the following
-        # rules, even if there are alternate valid encodings for the same message.
-        # - Fields are serialized in tag order.
-        # - There are no unknown fields.
-        # - There are no duplicate fields.
-        # - Fields are serialized according to the default semantics for their type.
+        # rules, even if there are alternate valid encodings for the same message:
+        # * Fields are serialized in tag order.
+        # * There are no unknown fields.
+        # * There are no duplicate fields.
+        # * Fields are serialized according to the default semantics for their type.
         # Most protocol buffer implementations will always follow these rules when
         # serializing, but care should be taken to avoid shortcuts. For instance,
         # concatenating two messages to merge them may produce duplicate fields.
@@ -1252,8 +1266,8 @@ module Google
       # external context of the request. The server may use this for logging or other
       # purposes. To use it, the client attaches the header to the call using the
       # canonical proto serialization:
-      # name: build.bazel.remote.execution.v2.requestmetadata-bin
-      # contents: the base64 encoded binary RequestMetadata message.
+      # * name: `build.bazel.remote.execution.v2.requestmetadata-bin`
+      # * contents: the base64 encoded binary `RequestMetadata` message.
       class BuildBazelRemoteExecutionV2RequestMetadata
         include Google::Apis::Core::Hashable
       
@@ -1373,10 +1387,10 @@ module Google
         # In order to ensure that two equivalent directory trees hash to the same
         # value, the following restrictions MUST be obeyed when constructing a
         # a `Directory`:
-        # - Every child in the directory must have a path of exactly one segment.
+        # * Every child in the directory must have a path of exactly one segment.
         # Multiple levels of directory hierarchy may not be collapsed.
-        # - Each child in the directory must have a unique path segment (file name).
-        # - The files, directories and symlinks in the directory must each be sorted
+        # * Each child in the directory must have a unique path segment (file name).
+        # * The files, directories and symlinks in the directory must each be sorted
         # in lexicographical order by path. The path strings must be sorted by code
         # point, equivalently, by UTF-8 bytes.
         # A `Directory` that obeys the restrictions is said to be in canonical form.
@@ -1720,6 +1734,12 @@ module Google
         # @return [String]
         attr_accessor :location
       
+        # Output only. Whether stack driver logging is enabled for the instance.
+        # Corresponds to the JSON property `loggingEnabled`
+        # @return [Boolean]
+        attr_accessor :logging_enabled
+        alias_method :logging_enabled?, :logging_enabled
+      
         # Output only. Instance resource name formatted as:
         # `projects/[PROJECT_ID]/instances/[INSTANCE_ID]`.
         # Name should not be populated when creating an instance since it is provided
@@ -1740,6 +1760,7 @@ module Google
         # Update properties of this object
         def update!(**args)
           @location = args[:location] if args.key?(:location)
+          @logging_enabled = args[:logging_enabled] if args.key?(:logging_enabled)
           @name = args[:name] if args.key?(:name)
           @state = args[:state] if args.key?(:state)
         end
@@ -1886,8 +1907,10 @@ module Google
         # @return [String]
         attr_accessor :min_cpu_platform
       
-        # Output only. `reserved=true` means the worker is reserved and won't be
-        # preempted.
+        # Determines whether the worker is reserved (and therefore won't be
+        # preempted).
+        # See [Preemptible VMs](https://cloud.google.com/preemptible-vms/) for more
+        # details.
         # Corresponds to the JSON property `reserved`
         # @return [Boolean]
         attr_accessor :reserved
@@ -3121,6 +3144,16 @@ module Google
         # @return [Fixnum]
         attr_accessor :exit_code
       
+        # Implementation-dependent metadata about the task. Both servers and bots
+        # may define messages which can be encoded here; bots are free to provide
+        # metadata in multiple formats, and servers are free to choose one or more
+        # of the values to process and ignore others. In particular, it is *not*
+        # considered an error for the bot to provide the server with a field that it
+        # doesn't know about.
+        # Corresponds to the JSON property `metadata`
+        # @return [Array<Hash<String,Object>>]
+        attr_accessor :metadata
+      
         # The CommandTask and CommandResult messages assume the existence of a service
         # that can serve blobs of content, identified by a hash and size known as a
         # "digest." The method by which these blobs may be retrieved is not specified
@@ -3139,16 +3172,6 @@ module Google
         # @return [String]
         attr_accessor :overhead
       
-        # Implementation-dependent statistics about the task. Both servers and bots
-        # may define messages which can be encoded here; bots are free to provide
-        # statistics in multiple formats, and servers are free to choose one or more
-        # of the values to process and ignore others. In particular, it is *not*
-        # considered an error for the bot to provide the server with a field that it
-        # doesn't know about.
-        # Corresponds to the JSON property `statistics`
-        # @return [Array<Hash<String,Object>>]
-        attr_accessor :statistics
-      
         # 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](https://github.com/grpc). The error model is designed to be:
@@ -3200,9 +3223,9 @@ module Google
         def update!(**args)
           @duration = args[:duration] if args.key?(:duration)
           @exit_code = args[:exit_code] if args.key?(:exit_code)
+          @metadata = args[:metadata] if args.key?(:metadata)
           @outputs = args[:outputs] if args.key?(:outputs)
           @overhead = args[:overhead] if args.key?(:overhead)
-          @statistics = args[:statistics] if args.key?(:statistics)
           @status = args[:status] if args.key?(:status)
         end
       end