# Generated by the protocol buffer compiler.  DO NOT EDIT!
# Source: google/ads/google_ads/v3/services/google_ads_service.proto for package 'Google::Ads::GoogleAds::V3::Services'
# Original file comments:
# Copyright 2020 Google LLC
#
# 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 'grpc'
require 'google/ads/google_ads/v3/services/google_ads_service_pb'

module Google::Ads::GoogleAds::V3::Services
  module GoogleAdsService
    # Proto file describing the GoogleAdsService.
    #
    # Service to fetch data and metrics across resources.
    class Service

      include GRPC::GenericService

      self.marshal_class_method = :encode
      self.unmarshal_class_method = :decode
      self.service_name = 'google.ads.googleads.v3.services.GoogleAdsService'

      # Returns all rows that match the search query.
      rpc :Search, SearchGoogleAdsRequest, SearchGoogleAdsResponse
      # Returns all rows that match the search stream query.
      rpc :SearchStream, SearchGoogleAdsStreamRequest, stream(SearchGoogleAdsStreamResponse)
      # Creates, updates, or removes resources. This method supports atomic
      # transactions with multiple types of resources. For example, you can
      # atomically create a campaign and a campaign budget, or perform up to
      # thousands of mutates atomically.
      #
      # This method is essentially a wrapper around a series of mutate methods. The
      # only features it offers over calling those methods directly are:
      #
      # - Atomic transactions
      # - Temp resource names (described below)
      # - Somewhat reduced latency over making a series of mutate calls
      #
      # Note: Only resources that support atomic transactions are included, so this
      # method can't replace all calls to individual services.
      #
      # ## Atomic Transaction Benefits
      #
      # Atomicity makes error handling much easier. If you're making a series of
      # changes and one fails, it can leave your account in an inconsistent state.
      # With atomicity, you either reach the desired state directly, or the request
      # fails and you can retry.
      #
      # ## Temp Resource Names
      #
      # Temp resource names are a special type of resource name used to create a
      # resource and reference that resource in the same request. For example, if a
      # campaign budget is created with `resource_name` equal to
      # `customers/123/campaignBudgets/-1`, that resource name can be reused in
      # the `Campaign.budget` field in the same request. That way, the two
      # resources are created and linked atomically.
      #
      # To create a temp resource name, put a negative number in the part of the
      # name that the server would normally allocate.
      #
      # Note:
      #
      # - Resources must be created with a temp name before the name can be reused.
      #   For example, the previous CampaignBudget+Campaign example would fail if
      #   the mutate order was reversed.
      # - Temp names are not remembered across requests.
      # - There's no limit to the number of temp names in a request.
      # - Each temp name must use a unique negative number, even if the resource
      #   types differ.
      #
      # ## Latency
      #
      # It's important to group mutates by resource type or the request may time
      # out and fail. Latency is roughly equal to a series of calls to individual
      # mutate methods, where each change in resource type is a new call. For
      # example, mutating 10 campaigns then 10 ad groups is like 2 calls, while
      # mutating 1 campaign, 1 ad group, 1 campaign, 1 ad group is like 4 calls.
      rpc :Mutate, MutateGoogleAdsRequest, MutateGoogleAdsResponse
    end

    Stub = Service.rpc_stub_class
  end
end