google-api-client 0.30.9 → 0.30.10

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

@@ -2256,7 +2256,9 @@ module Google
           attr_accessor :can_download
           alias_method :can_download?, :can_download
         
-          # Whether the current user can edit this file.
+          # Whether the current user can edit this file. Other factors may limit the type
+          # of changes a user can make to a file. For example, see
+          # canChangeCopyRequiresWriterPermission or canModifyContent.
           # Corresponds to the JSON property `canEdit`
           # @return [Boolean]
           attr_accessor :can_edit
@@ -2269,6 +2271,12 @@ module Google
           attr_accessor :can_list_children
           alias_method :can_list_children?, :can_list_children
         
+          # Whether the current user can modify the content of this file.
+          # Corresponds to the JSON property `canModifyContent`
+          # @return [Boolean]
+          attr_accessor :can_modify_content
+          alias_method :can_modify_content?, :can_modify_content
+        
           # Whether the current user can move children of this folder outside of the
           # shared drive. This is false when the item is not a folder. Only populated for
           # items in shared drives.
@@ -2413,6 +2421,7 @@ module Google
             @can_download = args[:can_download] if args.key?(:can_download)
             @can_edit = args[:can_edit] if args.key?(:can_edit)
             @can_list_children = args[:can_list_children] if args.key?(:can_list_children)
+            @can_modify_content = args[:can_modify_content] if args.key?(:can_modify_content)
             @can_move_children_out_of_drive = args[:can_move_children_out_of_drive] if args.key?(:can_move_children_out_of_drive)
             @can_move_children_out_of_team_drive = args[:can_move_children_out_of_team_drive] if args.key?(:can_move_children_out_of_team_drive)
             @can_move_children_within_drive = args[:can_move_children_within_drive] if args.key?(:can_move_children_within_drive)

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

@@ -869,6 +869,7 @@ module Google
             property :can_download, as: 'canDownload'
             property :can_edit, as: 'canEdit'
             property :can_list_children, as: 'canListChildren'
+            property :can_modify_content, as: 'canModifyContent'
             property :can_move_children_out_of_drive, as: 'canMoveChildrenOutOfDrive'
             property :can_move_children_out_of_team_drive, as: 'canMoveChildrenOutOfTeamDrive'
             property :can_move_children_within_drive, as: 'canMoveChildrenWithinDrive'

data/generated/google/apis/drive_v3.rb

@@ -26,7 +26,7 @@ module Google
     # @see https://developers.google.com/drive/
     module DriveV3
       VERSION = 'V3'
-      REVISION = '20190620'
+      REVISION = '20190822'
 
       # See, edit, create, and delete all of your Google Drive files
       AUTH_DRIVE = 'https://www.googleapis.com/auth/drive'

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

@@ -1414,7 +1414,9 @@ module Google
           attr_accessor :can_download
           alias_method :can_download?, :can_download
         
-          # Whether the current user can edit this file.
+          # Whether the current user can edit this file. Other factors may limit the type
+          # of changes a user can make to a file. For example, see
+          # canChangeCopyRequiresWriterPermission or canModifyContent.
           # Corresponds to the JSON property `canEdit`
           # @return [Boolean]
           attr_accessor :can_edit
@@ -1427,6 +1429,12 @@ module Google
           attr_accessor :can_list_children
           alias_method :can_list_children?, :can_list_children
         
+          # Whether the current user can modify the content of this file.
+          # Corresponds to the JSON property `canModifyContent`
+          # @return [Boolean]
+          attr_accessor :can_modify_content
+          alias_method :can_modify_content?, :can_modify_content
+        
           # Whether the current user can move children of this folder outside of the
           # shared drive. This is false when the item is not a folder. Only populated for
           # items in shared drives.
@@ -1571,6 +1579,7 @@ module Google
             @can_download = args[:can_download] if args.key?(:can_download)
             @can_edit = args[:can_edit] if args.key?(:can_edit)
             @can_list_children = args[:can_list_children] if args.key?(:can_list_children)
+            @can_modify_content = args[:can_modify_content] if args.key?(:can_modify_content)
             @can_move_children_out_of_drive = args[:can_move_children_out_of_drive] if args.key?(:can_move_children_out_of_drive)
             @can_move_children_out_of_team_drive = args[:can_move_children_out_of_team_drive] if args.key?(:can_move_children_out_of_team_drive)
             @can_move_children_within_drive = args[:can_move_children_within_drive] if args.key?(:can_move_children_within_drive)

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

@@ -567,6 +567,7 @@ module Google
             property :can_download, as: 'canDownload'
             property :can_edit, as: 'canEdit'
             property :can_list_children, as: 'canListChildren'
+            property :can_modify_content, as: 'canModifyContent'
             property :can_move_children_out_of_drive, as: 'canMoveChildrenOutOfDrive'
             property :can_move_children_out_of_team_drive, as: 'canMoveChildrenOutOfTeamDrive'
             property :can_move_children_within_drive, as: 'canMoveChildrenWithinDrive'

data/generated/google/apis/driveactivity_v2.rb

@@ -25,7 +25,7 @@ module Google
     # @see https://developers.google.com/drive/activity/
     module DriveactivityV2
       VERSION = 'V2'
-      REVISION = '20190423'
+      REVISION = '20190907'
 
       # View and add to the activity record of files in your Google Drive
       AUTH_DRIVE_ACTIVITY = 'https://www.googleapis.com/auth/drive.activity'

data/generated/google/apis/firestore_v1.rb

@@ -26,7 +26,7 @@ module Google
     # @see https://cloud.google.com/firestore
     module FirestoreV1
       VERSION = 'V1'
-      REVISION = '20190323'
+      REVISION = '20190804'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

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

@@ -1080,8 +1080,7 @@ module Google
         # @return [Array<Google::Apis::FirestoreV1::GoogleFirestoreAdminV1IndexField>]
         attr_accessor :fields
       
-        # Output only.
-        # A server defined name for this index.
+        # Output only. A server defined name for this index.
         # The form of this name for composite indexes will be:
         # `projects/`project_id`/databases/`database_id`/collectionGroups/`collection_id`
         # /indexes/`composite_index_id``
@@ -1100,8 +1099,7 @@ module Google
         # @return [String]
         attr_accessor :query_scope
       
-        # Output only.
-        # The serving state of the index.
+        # Output only. The serving state of the index.
         # Corresponds to the JSON property `state`
         # @return [String]
         attr_accessor :state
@@ -1123,8 +1121,8 @@ module Google
       class GoogleFirestoreAdminV1IndexConfig
         include Google::Apis::Core::Hashable
       
-        # Output only.
-        # Specifies the resource name of the `Field` from which this field's
+        # Output only. Specifies the resource name of the `Field` from which this field'
+        # s
         # index configuration is set (when `uses_ancestor_config` is true),
         # or from which it *would* be set if this field had no index configuration
         # (when `uses_ancestor_config` is false).
@@ -1147,8 +1145,7 @@ module Google
         attr_accessor :reverting
         alias_method :reverting?, :reverting
       
-        # Output only.
-        # When true, the `Field`'s index configuration is set from the
+        # Output only. When true, the `Field`'s index configuration is set from the
         # configuration specified by the `ancestor_field`.
         # When false, the `Field`'s index configuration is defined explicitly.
         # Corresponds to the JSON property `usesAncestorConfig`
@@ -1433,43 +1430,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 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 package `google.rpc` that can be used for common error conditions.
-        # # Language mapping
-        # The `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 uses
-        # The 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.
+        # used by [gRPC](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::FirestoreV1::Status]
         attr_accessor :error
@@ -1484,7 +1448,7 @@ module Google
       
         # The server-assigned name, which is only unique within the same service that
         # originally returns it. If you use the default HTTP mapping, the
-        # `name` should have the format of `operations/some/unique/name`.
+        # `name` should be a resource name ending with `operations/`unique_id``.
         # Corresponds to the JSON property `name`
         # @return [String]
         attr_accessor :name
@@ -2055,43 +2019,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 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 package `google.rpc` that can be used for common error conditions.
-      # # Language mapping
-      # The `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 uses
-      # The 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.
+      # used by [gRPC](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
       
@@ -2236,12 +2167,8 @@ module Google
         # @return [String]
         attr_accessor :resume_token
       
-        # A client provided target ID.
-        # If not set, the server will assign an ID for the target.
-        # Used for resuming a target without changing IDs. The IDs can either be
-        # client-assigned or be server-assigned in a previous stream. All targets
-        # with client provided IDs must be added before adding a target that needs
-        # a server-assigned id.
+        # The target ID that identifies the target on the stream. Must be a positive
+        # number and non-zero.
         # Corresponds to the JSON property `targetId`
         # @return [Fixnum]
         attr_accessor :target_id
@@ -2267,43 +2194,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 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 package `google.rpc` that can be used for common error conditions.
-        # # Language mapping
-        # The `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 uses
-        # The 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.
+        # used by [gRPC](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 `cause`
         # @return [Google::Apis::FirestoreV1::Status]
         attr_accessor :cause
@@ -2335,10 +2229,7 @@ module Google
       
         # The target IDs of targets that have changed.
         # If empty, the change applies to all targets.
-        # For `target_change_type=ADD`, the order of the target IDs matches the order
-        # of the requests to add the targets. This allows clients to unambiguously
-        # associate server-assigned target IDs with added targets.
-        # For other states, the order of the target IDs is not defined.
+        # The order of the target IDs is not defined.
         # Corresponds to the JSON property `targetIds`
         # @return [Array<Fixnum>]
         attr_accessor :target_ids

data/generated/google/apis/firestore_v1beta1.rb

@@ -26,7 +26,7 @@ module Google
     # @see https://cloud.google.com/firestore
     module FirestoreV1beta1
       VERSION = 'V1beta1'
-      REVISION = '20190323'
+      REVISION = '20190804'
 
       # View and manage your data across Google Cloud Platform services
       AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform'

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

@@ -1140,43 +1140,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 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 package `google.rpc` that can be used for common error conditions.
-        # # Language mapping
-        # The `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 uses
-        # The 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.
+        # used by [gRPC](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::FirestoreV1beta1::Status]
         attr_accessor :error
@@ -1191,7 +1158,7 @@ module Google
       
         # The server-assigned name, which is only unique within the same service that
         # originally returns it. If you use the default HTTP mapping, the
-        # `name` should have the format of `operations/some/unique/name`.
+        # `name` should be a resource name ending with `operations/`unique_id``.
         # Corresponds to the JSON property `name`
         # @return [String]
         attr_accessor :name
@@ -1690,43 +1657,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 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 package `google.rpc` that can be used for common error conditions.
-      # # Language mapping
-      # The `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 uses
-      # The 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.
+      # used by [gRPC](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
       
@@ -1871,12 +1805,8 @@ module Google
         # @return [String]
         attr_accessor :resume_token
       
-        # A client provided target ID.
-        # If not set, the server will assign an ID for the target.
-        # Used for resuming a target without changing IDs. The IDs can either be
-        # client-assigned or be server-assigned in a previous stream. All targets
-        # with client provided IDs must be added before adding a target that needs
-        # a server-assigned id.
+        # The target ID that identifies the target on the stream. Must be a positive
+        # number and non-zero.
         # Corresponds to the JSON property `targetId`
         # @return [Fixnum]
         attr_accessor :target_id
@@ -1902,43 +1832,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 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 package `google.rpc` that can be used for common error conditions.
-        # # Language mapping
-        # The `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 uses
-        # The 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.
+        # used by [gRPC](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 `cause`
         # @return [Google::Apis::FirestoreV1beta1::Status]
         attr_accessor :cause
@@ -1970,10 +1867,7 @@ module Google
       
         # The target IDs of targets that have changed.
         # If empty, the change applies to all targets.
-        # For `target_change_type=ADD`, the order of the target IDs matches the order
-        # of the requests to add the targets. This allows clients to unambiguously
-        # associate server-assigned target IDs with added targets.
-        # For other states, the order of the target IDs is not defined.
+        # The order of the target IDs is not defined.
         # Corresponds to the JSON property `targetIds`
         # @return [Array<Fixnum>]
         attr_accessor :target_ids