google-api-client 0.30.1 → 0.30.2

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

@@ -51,6 +51,45 @@ module Google
           @batch_path = 'batch/androidenterprise/v1'
         end
         
+        # Uploads a report containing any changes in app states on the device since the
+        # last report was generated. You can call this method up to 3 times every 24
+        # hours for a given device.
+        # @param [String] enterprise_id
+        #   The ID of the enterprise.
+        # @param [String] user_id
+        #   The ID of the user.
+        # @param [String] device_id
+        #   The ID of the device.
+        # @param [String] fields
+        #   Selector specifying which fields to include in a partial response.
+        # @param [String] quota_user
+        #   An opaque string that represents a user for quota purposes. Must not exceed 40
+        #   characters.
+        # @param [String] user_ip
+        #   Deprecated. Please use quotaUser instead.
+        # @param [Google::Apis::RequestOptions] options
+        #   Request-specific options
+        #
+        # @yield [result, err] Result & error if block supplied
+        # @yieldparam result [NilClass] No result returned for this method
+        # @yieldparam err [StandardError] error object if request failed
+        #
+        # @return [void]
+        #
+        # @raise [Google::Apis::ServerError] An error occurred on the server and the request can be retried
+        # @raise [Google::Apis::ClientError] The request is invalid and should not be retried without modification
+        # @raise [Google::Apis::AuthorizationError] Authorization is required
+        def force_device_report_upload(enterprise_id, user_id, device_id, fields: nil, quota_user: nil, user_ip: nil, options: nil, &block)
+          command = make_simple_command(:post, 'enterprises/{enterpriseId}/users/{userId}/devices/{deviceId}/forceReportUpload', options)
+          command.params['enterpriseId'] = enterprise_id unless enterprise_id.nil?
+          command.params['userId'] = user_id unless user_id.nil?
+          command.params['deviceId'] = device_id unless device_id.nil?
+          command.query['fields'] = fields unless fields.nil?
+          command.query['quotaUser'] = quota_user unless quota_user.nil?
+          command.query['userIp'] = user_ip unless user_ip.nil?
+          execute_or_queue_command(command, &block)
+        end
+        
         # Retrieves the details of a device.
         # @param [String] enterprise_id
         #   The ID of the enterprise.

data/generated/google/apis/androidpublisher_v3.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://developers.google.com/android-publisher
     module AndroidpublisherV3
       VERSION = 'V3'
-      REVISION = '20190508'
+      REVISION = '20190604'
 
       # View and manage your Google Play Developer account
       AUTH_ANDROIDPUBLISHER = 'https://www.googleapis.com/auth/androidpublisher'

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

@@ -1482,6 +1482,13 @@ module Google
       class SubscriptionPurchase
         include Google::Apis::Core::Hashable
       
+        # The acknowledgement state of the subscription product. Possible values are:
+        # - Yet to be acknowledged
+        # - Acknowledged
+        # Corresponds to the JSON property `acknowledgementState`
+        # @return [Fixnum]
+        attr_accessor :acknowledgement_state
+      
         # Whether the subscription will automatically be renewed when it reaches its
         # current expiry time.
         # Corresponds to the JSON property `autoRenewing`
@@ -1642,6 +1649,7 @@ module Google
       
         # Update properties of this object
         def update!(**args)
+          @acknowledgement_state = args[:acknowledgement_state] if args.key?(:acknowledgement_state)
           @auto_renewing = args[:auto_renewing] if args.key?(:auto_renewing)
           @auto_resume_time_millis = args[:auto_resume_time_millis] if args.key?(:auto_resume_time_millis)
           @cancel_reason = args[:cancel_reason] if args.key?(:cancel_reason)

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

@@ -808,6 +808,7 @@ module Google
       class SubscriptionPurchase
         # @private
         class Representation < Google::Apis::Core::JsonRepresentation
+          property :acknowledgement_state, as: 'acknowledgementState'
           property :auto_renewing, as: 'autoRenewing'
           property :auto_resume_time_millis, :numeric_string => true, as: 'autoResumeTimeMillis'
           property :cancel_reason, as: 'cancelReason'

data/generated/google/apis/appengine_v1.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://cloud.google.com/appengine/docs/admin-api/
     module AppengineV1
       VERSION = 'V1'
-      REVISION = '20190503'
+      REVISION = '20190531'
 
       # View and manage your applications deployed on Google App Engine
       AUTH_APPENGINE_ADMIN = 'https://www.googleapis.com/auth/appengine.admin'

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

@@ -1796,38 +1796,10 @@ module Google
       
         # 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:
-        # Simple to use and understand for most users
-        # Flexible enough to meet unexpected needsOverviewThe 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 package google.rpc that can be used for common error
-        # conditions.Language mappingThe Status message is the logical representation of
-        # the error model, but it is not necessarily the actual wire format. When the
-        # Status 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 usesThe error model and the Status 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.
+        # (https://github.com/grpc). Each Status message contains three pieces of data:
+        # error code, error message, and error details.You can find out more about this
+        # error model and how to work with it in the API Design Guide (https://cloud.
+        # google.com/apis/design/errors).
         # Corresponds to the JSON property `error`
         # @return [Google::Apis::AppengineV1::Status]
         attr_accessor :error
@@ -2445,38 +2417,10 @@ module Google
       
       # 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:
-      # Simple to use and understand for most users
-      # Flexible enough to meet unexpected needsOverviewThe 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 package google.rpc that can be used for common error
-      # conditions.Language mappingThe Status message is the logical representation of
-      # the error model, but it is not necessarily the actual wire format. When the
-      # Status 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 usesThe error model and the Status 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.
+      # (https://github.com/grpc). Each Status message contains three pieces of data:
+      # error code, error message, and error details.You can find out more about this
+      # error model and how to work with it in the API Design Guide (https://cloud.
+      # google.com/apis/design/errors).
       class Status
         include Google::Apis::Core::Hashable
       

data/generated/google/apis/appengine_v1alpha.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://cloud.google.com/appengine/docs/admin-api/
     module AppengineV1alpha
       VERSION = 'V1alpha'
-      REVISION = '20190503'
+      REVISION = '20190531'
 
       # View and manage your applications deployed on Google App Engine
       AUTH_APPENGINE_ADMIN = 'https://www.googleapis.com/auth/appengine.admin'

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

@@ -528,38 +528,10 @@ module Google
       
         # 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:
-        # Simple to use and understand for most users
-        # Flexible enough to meet unexpected needsOverviewThe 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 package google.rpc that can be used for common error
-        # conditions.Language mappingThe Status message is the logical representation of
-        # the error model, but it is not necessarily the actual wire format. When the
-        # Status 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 usesThe error model and the Status 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.
+        # (https://github.com/grpc). Each Status message contains three pieces of data:
+        # error code, error message, and error details.You can find out more about this
+        # error model and how to work with it in the API Design Guide (https://cloud.
+        # google.com/apis/design/errors).
         # Corresponds to the JSON property `error`
         # @return [Google::Apis::AppengineV1alpha::Status]
         attr_accessor :error
@@ -867,38 +839,10 @@ module Google
       
       # 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:
-      # Simple to use and understand for most users
-      # Flexible enough to meet unexpected needsOverviewThe 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 package google.rpc that can be used for common error
-      # conditions.Language mappingThe Status message is the logical representation of
-      # the error model, but it is not necessarily the actual wire format. When the
-      # Status 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 usesThe error model and the Status 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.
+      # (https://github.com/grpc). Each Status message contains three pieces of data:
+      # error code, error message, and error details.You can find out more about this
+      # error model and how to work with it in the API Design Guide (https://cloud.
+      # google.com/apis/design/errors).
       class Status
         include Google::Apis::Core::Hashable
       

data/generated/google/apis/appengine_v1beta.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://cloud.google.com/appengine/docs/admin-api/
     module AppengineV1beta
       VERSION = 'V1beta'
-      REVISION = '20190503'
+      REVISION = '20190531'
 
       # View and manage your applications deployed on Google App Engine
       AUTH_APPENGINE_ADMIN = 'https://www.googleapis.com/auth/appengine.admin'

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

@@ -1913,38 +1913,10 @@ module Google
       
         # 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:
-        # Simple to use and understand for most users
-        # Flexible enough to meet unexpected needsOverviewThe 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 package google.rpc that can be used for common error
-        # conditions.Language mappingThe Status message is the logical representation of
-        # the error model, but it is not necessarily the actual wire format. When the
-        # Status 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 usesThe error model and the Status 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.
+        # (https://github.com/grpc). Each Status message contains three pieces of data:
+        # error code, error message, and error details.You can find out more about this
+        # error model and how to work with it in the API Design Guide (https://cloud.
+        # google.com/apis/design/errors).
         # Corresponds to the JSON property `error`
         # @return [Google::Apis::AppengineV1beta::Status]
         attr_accessor :error
@@ -2562,38 +2534,10 @@ module Google
       
       # 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:
-      # Simple to use and understand for most users
-      # Flexible enough to meet unexpected needsOverviewThe 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 package google.rpc that can be used for common error
-      # conditions.Language mappingThe Status message is the logical representation of
-      # the error model, but it is not necessarily the actual wire format. When the
-      # Status 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 usesThe error model and the Status 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.
+      # (https://github.com/grpc). Each Status message contains three pieces of data:
+      # error code, error message, and error details.You can find out more about this
+      # error model and how to work with it in the API Design Guide (https://cloud.
+      # google.com/apis/design/errors).
       class Status
         include Google::Apis::Core::Hashable
       

data/generated/google/apis/bigquery_v2.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://cloud.google.com/bigquery/
     module BigqueryV2
       VERSION = 'V2'
-      REVISION = '20190510'
+      REVISION = '20190530'
 
       # View and manage your data in Google BigQuery
       AUTH_BIGQUERY = 'https://www.googleapis.com/auth/bigquery'

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

@@ -311,6 +311,16 @@ module Google
         # @return [Array<Google::Apis::BigqueryV2::BinaryConfusionMatrix>]
         attr_accessor :binary_confusion_matrix_list
       
+        # Label representing the negative class.
+        # Corresponds to the JSON property `negativeLabel`
+        # @return [String]
+        attr_accessor :negative_label
+      
+        # Label representing the positive class.
+        # Corresponds to the JSON property `positiveLabel`
+        # @return [String]
+        attr_accessor :positive_label
+      
         def initialize(**args)
            update!(**args)
         end
@@ -319,6 +329,8 @@ module Google
         def update!(**args)
           @aggregate_classification_metrics = args[:aggregate_classification_metrics] if args.key?(:aggregate_classification_metrics)
           @binary_confusion_matrix_list = args[:binary_confusion_matrix_list] if args.key?(:binary_confusion_matrix_list)
+          @negative_label = args[:negative_label] if args.key?(:negative_label)
+          @positive_label = args[:positive_label] if args.key?(:positive_label)
         end
       end
       
@@ -3160,7 +3172,6 @@ module Google
         attr_accessor :creation_time
       
         # [Optional] A user-friendly description of this model.
-        # @mutable bigquery.models.patch
         # Corresponds to the JSON property `description`
         # @return [String]
         attr_accessor :description
@@ -3175,7 +3186,6 @@ module Google
         # will be deleted and their storage reclaimed.  The defaultTableExpirationMs
         # property of the encapsulating dataset can be used to set a default
         # expirationTime on newly created models.
-        # @mutable bigquery.models.patch
         # Corresponds to the JSON property `expirationTime`
         # @return [Fixnum]
         attr_accessor :expiration_time
@@ -3186,7 +3196,6 @@ module Google
         attr_accessor :feature_columns
       
         # [Optional] A descriptive name for this model.
-        # @mutable bigquery.models.patch
         # Corresponds to the JSON property `friendlyName`
         # @return [String]
         attr_accessor :friendly_name
@@ -3203,7 +3212,6 @@ module Google
         # characters, underscores and dashes. International characters are allowed.
         # Label values are optional. Label keys must start with a letter and each
         # label in the list must have a different key.
-        # @mutable bigquery.models.patch
         # Corresponds to the JSON property `labels`
         # @return [Hash<String,String>]
         attr_accessor :labels

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

@@ -660,6 +660,8 @@ module Google
       
           collection :binary_confusion_matrix_list, as: 'binaryConfusionMatrixList', class: Google::Apis::BigqueryV2::BinaryConfusionMatrix, decorator: Google::Apis::BigqueryV2::BinaryConfusionMatrix::Representation
       
+          property :negative_label, as: 'negativeLabel'
+          property :positive_label, as: 'positiveLabel'
         end
       end