Autogenerated update (2019-02-03)

Update:
- servicecontrol_v1
This commit is contained in:
Google APIs 2019-02-03 00:36:27 +00:00
parent bc314dbf16
commit 814c3435dd
8 changed files with 28095 additions and 1 deletions

File diff suppressed because it is too large Load Diff

View File

@ -0,0 +1,40 @@
# Copyright 2015 Google Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
require 'google/apis/dfareporting_v3_3/service.rb'
require 'google/apis/dfareporting_v3_3/classes.rb'
require 'google/apis/dfareporting_v3_3/representations.rb'
module Google
module Apis
# DCM/DFA Reporting And Trafficking API
#
# Manages your DoubleClick Campaign Manager ad campaigns and reports.
#
# @see https://developers.google.com/doubleclick-advertisers/
module DfareportingV3_3
VERSION = 'V3_3'
REVISION = '20190124'
# Manage DoubleClick Digital Marketing conversions
AUTH_DDMCONVERSIONS = 'https://www.googleapis.com/auth/ddmconversions'
# View and manage DoubleClick for Advertisers reports
AUTH_DFAREPORTING = 'https://www.googleapis.com/auth/dfareporting'
# View and manage your DoubleClick Campaign Manager's (DCM) display ad campaigns
AUTH_DFATRAFFICKING = 'https://www.googleapis.com/auth/dfatrafficking'
end
end
end

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

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

View File

@ -474,6 +474,49 @@ module Google
# @return [String]
attr_accessor :detail
# 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.
# Corresponds to the JSON property `status`
# @return [Google::Apis::ServicecontrolV1::Status]
attr_accessor :status
# Subject to whom this error applies. See the specific code enum for more
# details on this field. For example:
# - “project:<project-id or project-number>”
@ -491,6 +534,7 @@ module Google
def update!(**args)
@code = args[:code] if args.key?(:code)
@detail = args[:detail] if args.key?(:detail)
@status = args[:status] if args.key?(:status)
@subject = args[:subject] if args.key?(:subject)
end
end

View File

@ -342,6 +342,8 @@ module Google
class Representation < Google::Apis::Core::JsonRepresentation
property :code, as: 'code'
property :detail, as: 'detail'
property :status, as: 'status', class: Google::Apis::ServicecontrolV1::Status, decorator: Google::Apis::ServicecontrolV1::Status::Representation
property :subject, as: 'subject'
end
end