From 471ff6cadf68792c3f142c5ee4b0182137421bb0 Mon Sep 17 00:00:00 2001 From: Google APIs Date: Wed, 19 Jun 2019 00:37:48 +0000 Subject: [PATCH] Autogenerated update (2019-06-19) Update: - accesscontextmanager_v1beta - cloudasset_v1 - cloudasset_v1beta1 - cloudfunctions_v1 - cloudfunctions_v1beta2 - commentanalyzer_v1alpha1 - toolresults_v1beta3 --- .../apis/accesscontextmanager_v1beta.rb | 2 +- .../accesscontextmanager_v1beta/classes.rb | 108 ++++++++++++++++++ .../representations.rb | 48 ++++++++ generated/google/apis/cloudasset_v1.rb | 2 +- .../google/apis/cloudasset_v1/classes.rb | 84 ++------------ generated/google/apis/cloudasset_v1beta1.rb | 2 +- .../google/apis/cloudasset_v1beta1/classes.rb | 84 ++------------ generated/google/apis/cloudfunctions_v1.rb | 2 +- .../google/apis/cloudfunctions_v1/classes.rb | 82 ++----------- .../google/apis/cloudfunctions_v1beta2.rb | 2 +- .../apis/cloudfunctions_v1beta2/classes.rb | 82 ++----------- .../google/apis/commentanalyzer_v1alpha1.rb | 4 +- .../apis/commentanalyzer_v1alpha1/service.rb | 2 +- generated/google/apis/toolresults_v1beta3.rb | 2 +- .../apis/toolresults_v1beta3/classes.rb | 35 ++++++ .../toolresults_v1beta3/representations.rb | 2 + 16 files changed, 236 insertions(+), 307 deletions(-) diff --git a/generated/google/apis/accesscontextmanager_v1beta.rb b/generated/google/apis/accesscontextmanager_v1beta.rb index de5b66610..18bfbd391 100644 --- a/generated/google/apis/accesscontextmanager_v1beta.rb +++ b/generated/google/apis/accesscontextmanager_v1beta.rb @@ -25,7 +25,7 @@ module Google # @see https://cloud.google.com/access-context-manager/docs/reference/rest/ module AccesscontextmanagerV1beta VERSION = 'V1beta' - REVISION = '20190529' + REVISION = '20190617' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/accesscontextmanager_v1beta/classes.rb b/generated/google/apis/accesscontextmanager_v1beta/classes.rb index e5fbb13fb..da20527d0 100644 --- a/generated/google/apis/accesscontextmanager_v1beta/classes.rb +++ b/generated/google/apis/accesscontextmanager_v1beta/classes.rb @@ -153,6 +153,35 @@ module Google end end + # Alpha. Specifies which services are granted access via this Bridge Service + # Perimeter. + class BridgeServiceRestriction + include Google::Apis::Core::Hashable + + # The list of APIs usable through the Bridge Perimeter. Must be empty + # unless 'enable_restriction' is True. + # Corresponds to the JSON property `allowedServices` + # @return [Array] + attr_accessor :allowed_services + + # Whether to restrict the set of APIs callable through the Bridge Service + # Perimeter. + # Corresponds to the JSON property `enableRestriction` + # @return [Boolean] + attr_accessor :enable_restriction + alias_method :enable_restriction?, :enable_restriction + + def initialize(**args) + update!(**args) + end + + # Update properties of this object + def update!(**args) + @allowed_services = args[:allowed_services] if args.key?(:allowed_services) + @enable_restriction = args[:enable_restriction] if args.key?(:enable_restriction) + end + end + # A condition necessary for an `AccessLevel` to be granted. The Condition is an # AND over its fields. So a Condition is true if: 1) the request IP is from one # of the listed subnetworks AND 2) the originating device complies with the @@ -296,6 +325,35 @@ module Google end end + # Alpha. Specifies how Access Levels are to be used for accessing the Service + # Perimeter. + class IngressServiceRestriction + include Google::Apis::Core::Hashable + + # The list of APIs usable with a valid Access Level. Must be empty unless + # 'enable_restriction' is True. + # Corresponds to the JSON property `allowedServices` + # @return [Array] + attr_accessor :allowed_services + + # Whether to restrict the set of APIs callable outside the Service + # Perimeter via Access Levels. + # Corresponds to the JSON property `enableRestriction` + # @return [Boolean] + attr_accessor :enable_restriction + alias_method :enable_restriction?, :enable_restriction + + def initialize(**args) + update!(**args) + end + + # Update properties of this object + def update!(**args) + @allowed_services = args[:allowed_services] if args.key?(:allowed_services) + @enable_restriction = args[:enable_restriction] if args.key?(:enable_restriction) + end + end + # A response to `ListAccessLevelsRequest`. class ListAccessLevelsResponse include Google::Apis::Core::Hashable @@ -564,6 +622,18 @@ module Google # @return [Array] attr_accessor :access_levels + # Alpha. Specifies which services are granted access via this Bridge Service + # Perimeter. + # Corresponds to the JSON property `bridgeServiceRestriction` + # @return [Google::Apis::AccesscontextmanagerV1beta::BridgeServiceRestriction] + attr_accessor :bridge_service_restriction + + # Alpha. Specifies how Access Levels are to be used for accessing the Service + # Perimeter. + # Corresponds to the JSON property `ingressServiceRestriction` + # @return [Google::Apis::AccesscontextmanagerV1beta::IngressServiceRestriction] + attr_accessor :ingress_service_restriction + # A list of GCP resources that are inside of the service perimeter. # Currently only projects are allowed. Format: `projects/`project_number`` # Corresponds to the JSON property `resources` @@ -586,6 +656,12 @@ module Google # @return [Array] attr_accessor :unrestricted_services + # Alpha. Specifies how APIs are allowed to communicate within the Service + # Perimeter. + # Corresponds to the JSON property `vpcServiceRestriction` + # @return [Google::Apis::AccesscontextmanagerV1beta::VpcServiceRestriction] + attr_accessor :vpc_service_restriction + def initialize(**args) update!(**args) end @@ -593,9 +669,12 @@ module Google # Update properties of this object def update!(**args) @access_levels = args[:access_levels] if args.key?(:access_levels) + @bridge_service_restriction = args[:bridge_service_restriction] if args.key?(:bridge_service_restriction) + @ingress_service_restriction = args[:ingress_service_restriction] if args.key?(:ingress_service_restriction) @resources = args[:resources] if args.key?(:resources) @restricted_services = args[:restricted_services] if args.key?(:restricted_services) @unrestricted_services = args[:unrestricted_services] if args.key?(:unrestricted_services) + @vpc_service_restriction = args[:vpc_service_restriction] if args.key?(:vpc_service_restriction) end end @@ -637,6 +716,35 @@ module Google @message = args[:message] if args.key?(:message) end end + + # Alpha. Specifies how APIs are allowed to communicate within the Service + # Perimeter. + class VpcServiceRestriction + include Google::Apis::Core::Hashable + + # The list of APIs usable within the Service Perimeter. Must be empty + # unless 'enable_restriction' is True. + # Corresponds to the JSON property `allowedServices` + # @return [Array] + attr_accessor :allowed_services + + # Whether to restrict API calls within the Service Perimeter to the list of + # APIs specified in 'allowed_services'. + # Corresponds to the JSON property `enableRestriction` + # @return [Boolean] + attr_accessor :enable_restriction + alias_method :enable_restriction?, :enable_restriction + + def initialize(**args) + update!(**args) + end + + # Update properties of this object + def update!(**args) + @allowed_services = args[:allowed_services] if args.key?(:allowed_services) + @enable_restriction = args[:enable_restriction] if args.key?(:enable_restriction) + end + end end end end diff --git a/generated/google/apis/accesscontextmanager_v1beta/representations.rb b/generated/google/apis/accesscontextmanager_v1beta/representations.rb index c5ce44650..78f7dfc24 100644 --- a/generated/google/apis/accesscontextmanager_v1beta/representations.rb +++ b/generated/google/apis/accesscontextmanager_v1beta/representations.rb @@ -40,6 +40,12 @@ module Google include Google::Apis::Core::JsonObjectSupport end + class BridgeServiceRestriction + class Representation < Google::Apis::Core::JsonRepresentation; end + + include Google::Apis::Core::JsonObjectSupport + end + class Condition class Representation < Google::Apis::Core::JsonRepresentation; end @@ -52,6 +58,12 @@ module Google include Google::Apis::Core::JsonObjectSupport end + class IngressServiceRestriction + class Representation < Google::Apis::Core::JsonRepresentation; end + + include Google::Apis::Core::JsonObjectSupport + end + class ListAccessLevelsResponse class Representation < Google::Apis::Core::JsonRepresentation; end @@ -100,6 +112,12 @@ module Google include Google::Apis::Core::JsonObjectSupport end + class VpcServiceRestriction + class Representation < Google::Apis::Core::JsonRepresentation; end + + include Google::Apis::Core::JsonObjectSupport + end + class AccessLevel # @private class Representation < Google::Apis::Core::JsonRepresentation @@ -133,6 +151,14 @@ module Google end end + class BridgeServiceRestriction + # @private + class Representation < Google::Apis::Core::JsonRepresentation + collection :allowed_services, as: 'allowedServices' + property :enable_restriction, as: 'enableRestriction' + end + end + class Condition # @private class Representation < Google::Apis::Core::JsonRepresentation @@ -159,6 +185,14 @@ module Google end end + class IngressServiceRestriction + # @private + class Representation < Google::Apis::Core::JsonRepresentation + collection :allowed_services, as: 'allowedServices' + property :enable_restriction, as: 'enableRestriction' + end + end + class ListAccessLevelsResponse # @private class Representation < Google::Apis::Core::JsonRepresentation @@ -225,9 +259,15 @@ module Google # @private class Representation < Google::Apis::Core::JsonRepresentation collection :access_levels, as: 'accessLevels' + property :bridge_service_restriction, as: 'bridgeServiceRestriction', class: Google::Apis::AccesscontextmanagerV1beta::BridgeServiceRestriction, decorator: Google::Apis::AccesscontextmanagerV1beta::BridgeServiceRestriction::Representation + + property :ingress_service_restriction, as: 'ingressServiceRestriction', class: Google::Apis::AccesscontextmanagerV1beta::IngressServiceRestriction, decorator: Google::Apis::AccesscontextmanagerV1beta::IngressServiceRestriction::Representation + collection :resources, as: 'resources' collection :restricted_services, as: 'restrictedServices' collection :unrestricted_services, as: 'unrestrictedServices' + property :vpc_service_restriction, as: 'vpcServiceRestriction', class: Google::Apis::AccesscontextmanagerV1beta::VpcServiceRestriction, decorator: Google::Apis::AccesscontextmanagerV1beta::VpcServiceRestriction::Representation + end end @@ -239,6 +279,14 @@ module Google property :message, as: 'message' end end + + class VpcServiceRestriction + # @private + class Representation < Google::Apis::Core::JsonRepresentation + collection :allowed_services, as: 'allowedServices' + property :enable_restriction, as: 'enableRestriction' + end + end end end end diff --git a/generated/google/apis/cloudasset_v1.rb b/generated/google/apis/cloudasset_v1.rb index 353c0e332..c0a82e704 100644 --- a/generated/google/apis/cloudasset_v1.rb +++ b/generated/google/apis/cloudasset_v1.rb @@ -25,7 +25,7 @@ module Google # @see https://cloud.google.com/resource-manager/docs/cloud-asset-inventory/quickstart-cloud-asset-inventory module CloudassetV1 VERSION = 'V1' - REVISION = '20190612' + REVISION = '20190615' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/cloudasset_v1/classes.rb b/generated/google/apis/cloudasset_v1/classes.rb index dd66f58e4..30cd2138c 100644 --- a/generated/google/apis/cloudasset_v1/classes.rb +++ b/generated/google/apis/cloudasset_v1/classes.rb @@ -430,43 +430,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::CloudassetV1::Status] attr_accessor :error @@ -481,7 +448,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 @@ -684,43 +651,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 diff --git a/generated/google/apis/cloudasset_v1beta1.rb b/generated/google/apis/cloudasset_v1beta1.rb index 3e23bb7e9..7ce65e14a 100644 --- a/generated/google/apis/cloudasset_v1beta1.rb +++ b/generated/google/apis/cloudasset_v1beta1.rb @@ -25,7 +25,7 @@ module Google # @see https://cloud.google.com/resource-manager/docs/cloud-asset-inventory/quickstart-cloud-asset-inventory module CloudassetV1beta1 VERSION = 'V1beta1' - REVISION = '20190612' + REVISION = '20190615' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/cloudasset_v1beta1/classes.rb b/generated/google/apis/cloudasset_v1beta1/classes.rb index 083efd8f6..4508bd263 100644 --- a/generated/google/apis/cloudasset_v1beta1/classes.rb +++ b/generated/google/apis/cloudasset_v1beta1/classes.rb @@ -429,43 +429,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::CloudassetV1beta1::Status] attr_accessor :error @@ -480,7 +447,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 @@ -683,43 +650,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 diff --git a/generated/google/apis/cloudfunctions_v1.rb b/generated/google/apis/cloudfunctions_v1.rb index 674fa6a1a..d8786f8f0 100644 --- a/generated/google/apis/cloudfunctions_v1.rb +++ b/generated/google/apis/cloudfunctions_v1.rb @@ -25,7 +25,7 @@ module Google # @see https://cloud.google.com/functions module CloudfunctionsV1 VERSION = 'V1' - REVISION = '20190529' + REVISION = '20190607' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/cloudfunctions_v1/classes.rb b/generated/google/apis/cloudfunctions_v1/classes.rb index 9685fce27..f70875228 100644 --- a/generated/google/apis/cloudfunctions_v1/classes.rb +++ b/generated/google/apis/cloudfunctions_v1/classes.rb @@ -786,43 +786,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::CloudfunctionsV1::Status] attr_accessor :error @@ -1165,43 +1132,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 diff --git a/generated/google/apis/cloudfunctions_v1beta2.rb b/generated/google/apis/cloudfunctions_v1beta2.rb index 39ebcdce9..4e81a0443 100644 --- a/generated/google/apis/cloudfunctions_v1beta2.rb +++ b/generated/google/apis/cloudfunctions_v1beta2.rb @@ -25,7 +25,7 @@ module Google # @see https://cloud.google.com/functions module CloudfunctionsV1beta2 VERSION = 'V1beta2' - REVISION = '20190508' + REVISION = '20190607' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/cloudfunctions_v1beta2/classes.rb b/generated/google/apis/cloudfunctions_v1beta2/classes.rb index 3bd4323f2..aef05a37d 100644 --- a/generated/google/apis/cloudfunctions_v1beta2/classes.rb +++ b/generated/google/apis/cloudfunctions_v1beta2/classes.rb @@ -578,43 +578,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::CloudfunctionsV1beta2::Status] attr_accessor :error @@ -829,43 +796,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 diff --git a/generated/google/apis/commentanalyzer_v1alpha1.rb b/generated/google/apis/commentanalyzer_v1alpha1.rb index b508bb9bb..9510fb674 100644 --- a/generated/google/apis/commentanalyzer_v1alpha1.rb +++ b/generated/google/apis/commentanalyzer_v1alpha1.rb @@ -27,10 +27,10 @@ module Google # doNotStore" flag to ensure that all submitted comments are automatically # deleted after scores are returned. # - # @see https://conversationai.github.io/ + # @see https://github.com/conversationai/perspectiveapi/blob/master/README.md module CommentanalyzerV1alpha1 VERSION = 'V1alpha1' - REVISION = '20190526' + REVISION = '20190616' # View your email address AUTH_USERINFO_EMAIL = 'https://www.googleapis.com/auth/userinfo.email' diff --git a/generated/google/apis/commentanalyzer_v1alpha1/service.rb b/generated/google/apis/commentanalyzer_v1alpha1/service.rb index dda691d20..42f7b8cf1 100644 --- a/generated/google/apis/commentanalyzer_v1alpha1/service.rb +++ b/generated/google/apis/commentanalyzer_v1alpha1/service.rb @@ -35,7 +35,7 @@ module Google # Commentanalyzer = Google::Apis::CommentanalyzerV1alpha1 # Alias the module # service = Commentanalyzer::CommentAnalyzerService.new # - # @see https://conversationai.github.io/ + # @see https://github.com/conversationai/perspectiveapi/blob/master/README.md class CommentAnalyzerService < Google::Apis::Core::BaseService # @return [String] # API key. Your API key identifies your project and provides you with API access, diff --git a/generated/google/apis/toolresults_v1beta3.rb b/generated/google/apis/toolresults_v1beta3.rb index c52158fd1..ff76b1600 100644 --- a/generated/google/apis/toolresults_v1beta3.rb +++ b/generated/google/apis/toolresults_v1beta3.rb @@ -25,7 +25,7 @@ module Google # @see https://firebase.google.com/docs/test-lab/ module ToolresultsV1beta3 VERSION = 'V1beta3' - REVISION = '20190612' + REVISION = '20190617' # View and manage your data across Google Cloud Platform services AUTH_CLOUD_PLATFORM = 'https://www.googleapis.com/auth/cloud-platform' diff --git a/generated/google/apis/toolresults_v1beta3/classes.rb b/generated/google/apis/toolresults_v1beta3/classes.rb index 98e2997d8..3512df54d 100644 --- a/generated/google/apis/toolresults_v1beta3/classes.rb +++ b/generated/google/apis/toolresults_v1beta3/classes.rb @@ -2618,6 +2618,40 @@ module Google class TestSuiteOverview include Google::Apis::Core::Hashable + # A Duration represents a signed, fixed-length span of time represented as a + # count of seconds and fractions of seconds at nanosecond resolution. It is + # independent of any calendar and concepts like "day" or "month". It is related + # to Timestamp in that the difference between two Timestamp values is a Duration + # and it can be added or subtracted from a Timestamp. Range is approximately +- + # 10,000 years. + # # Examples + # Example 1: Compute Duration from two Timestamps in pseudo code. + # Timestamp start = ...; Timestamp end = ...; Duration duration = ...; + # duration.seconds = end.seconds - start.seconds; duration.nanos = end.nanos - + # start.nanos; + # if (duration.seconds 0) ` duration.seconds += 1; duration.nanos -= 1000000000; + # ` else if (durations.seconds > 0 && duration.nanos < 0) ` duration.seconds -= + # 1; duration.nanos += 1000000000; ` + # Example 2: Compute Timestamp from Timestamp + Duration in pseudo code. + # Timestamp start = ...; Duration duration = ...; Timestamp end = ...; + # end.seconds = start.seconds + duration.seconds; end.nanos = start.nanos + + # duration.nanos; + # if (end.nanos = 1000000000) ` end.seconds += 1; end.nanos -= 1000000000; ` + # Example 3: Compute Duration from datetime.timedelta in Python. + # td = datetime.timedelta(days=3, minutes=10) duration = Duration() duration. + # FromTimedelta(td) + # # JSON Mapping + # In JSON format, the Duration type is encoded as a string rather than an object, + # where the string ends in the suffix "s" (indicating seconds) and is preceded + # by the number of seconds, with nanoseconds expressed as fractional seconds. + # For example, 3 seconds with 0 nanoseconds should be encoded in JSON format as " + # 3s", while 3 seconds and 1 nanosecond should be expressed in JSON format as "3. + # 000000001s", and 3 seconds and 1 microsecond should be expressed in JSON + # format as "3.000001s". + # Corresponds to the JSON property `elapsedTime` + # @return [Google::Apis::ToolresultsV1beta3::Duration] + attr_accessor :elapsed_time + # Number of test cases in error, typically set by the service by parsing the # xml_source. # - In create/response: always set - In update request: never @@ -2662,6 +2696,7 @@ module Google # Update properties of this object def update!(**args) + @elapsed_time = args[:elapsed_time] if args.key?(:elapsed_time) @error_count = args[:error_count] if args.key?(:error_count) @failure_count = args[:failure_count] if args.key?(:failure_count) @name = args[:name] if args.key?(:name) diff --git a/generated/google/apis/toolresults_v1beta3/representations.rb b/generated/google/apis/toolresults_v1beta3/representations.rb index a864d28c7..5c9710dc3 100644 --- a/generated/google/apis/toolresults_v1beta3/representations.rb +++ b/generated/google/apis/toolresults_v1beta3/representations.rb @@ -936,6 +936,8 @@ module Google class TestSuiteOverview # @private class Representation < Google::Apis::Core::JsonRepresentation + property :elapsed_time, as: 'elapsedTime', class: Google::Apis::ToolresultsV1beta3::Duration, decorator: Google::Apis::ToolresultsV1beta3::Duration::Representation + property :error_count, as: 'errorCount' property :failure_count, as: 'failureCount' property :name, as: 'name'