google-shopping-merchant-conversions-v1beta 0.a → 0.1.2
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.yardopts +12 -0
- data/AUTHENTICATION.md +122 -0
- data/README.md +143 -8
- data/lib/google/shopping/merchant/conversions/v1beta/conversion_sources_service/client.rb +928 -0
- data/lib/google/shopping/merchant/conversions/v1beta/conversion_sources_service/credentials.rb +49 -0
- data/lib/google/shopping/merchant/conversions/v1beta/conversion_sources_service/paths.rb +66 -0
- data/lib/google/shopping/merchant/conversions/v1beta/conversion_sources_service/rest/client.rb +860 -0
- data/lib/google/shopping/merchant/conversions/v1beta/conversion_sources_service/rest/service_stub.rb +428 -0
- data/lib/google/shopping/merchant/conversions/v1beta/conversion_sources_service/rest.rb +54 -0
- data/lib/google/shopping/merchant/conversions/v1beta/conversion_sources_service.rb +57 -0
- data/lib/google/shopping/merchant/conversions/v1beta/conversionsources_pb.rb +68 -0
- data/lib/google/shopping/merchant/conversions/v1beta/conversionsources_services_pb.rb +62 -0
- data/lib/google/shopping/merchant/conversions/v1beta/rest.rb +39 -0
- data/lib/google/shopping/merchant/conversions/v1beta/version.rb +7 -2
- data/lib/google/shopping/merchant/conversions/v1beta.rb +47 -0
- data/lib/google-shopping-merchant-conversions-v1beta.rb +21 -0
- data/proto_docs/README.md +4 -0
- data/proto_docs/google/api/client.rb +420 -0
- data/proto_docs/google/api/field_behavior.rb +85 -0
- data/proto_docs/google/api/launch_stage.rb +71 -0
- data/proto_docs/google/api/resource.rb +227 -0
- data/proto_docs/google/protobuf/duration.rb +98 -0
- data/proto_docs/google/protobuf/empty.rb +34 -0
- data/proto_docs/google/protobuf/field_mask.rb +229 -0
- data/proto_docs/google/protobuf/timestamp.rb +127 -0
- data/proto_docs/google/shopping/merchant/conversions/v1beta/conversionsources.rb +286 -0
- metadata +67 -10
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: ac2fa186989c321455f6300afc2bd6e1c84e4678a85903f7bdff2c1b49475548
|
4
|
+
data.tar.gz: 7a21dd5bc358c52e1855c4f19dc427a66f5d834418ab160fb81e21b3f409df39
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 6a8d2714cd79be62a773aa890037e61e947c3c628544da2f69058421c4c9fa4dfebbab013cbcd4ccd37706359aee42b6199b4be8d04f2592feea680db5164f83
|
7
|
+
data.tar.gz: ca6627b70c706d3ba64f3745eac742fd34eb964e1cc74fb402a8478e776194173b13fba6b49b3200746b167ae16d5e21e48c9260ff04d82194db4a121e0a41c6
|
data/.yardopts
ADDED
data/AUTHENTICATION.md
ADDED
@@ -0,0 +1,122 @@
|
|
1
|
+
# Authentication
|
2
|
+
|
3
|
+
The recommended way to authenticate to the google-shopping-merchant-conversions-v1beta library is to use
|
4
|
+
[Application Default Credentials (ADC)](https://cloud.google.com/docs/authentication/application-default-credentials).
|
5
|
+
To review all of your authentication options, see [Credentials lookup](#credential-lookup).
|
6
|
+
|
7
|
+
## Quickstart
|
8
|
+
|
9
|
+
The following example shows how to set up authentication for a local development
|
10
|
+
environment with your user credentials.
|
11
|
+
|
12
|
+
**NOTE:** This method is _not_ recommended for running in production. User credentials
|
13
|
+
should be used only during development.
|
14
|
+
|
15
|
+
1. [Download and install the Google Cloud CLI](https://cloud.google.com/sdk).
|
16
|
+
2. Set up a local ADC file with your user credentials:
|
17
|
+
|
18
|
+
```sh
|
19
|
+
gcloud auth application-default login
|
20
|
+
```
|
21
|
+
|
22
|
+
3. Write code as if already authenticated.
|
23
|
+
|
24
|
+
For more information about setting up authentication for a local development environment, see
|
25
|
+
[Set up Application Default Credentials](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-dev).
|
26
|
+
|
27
|
+
## Credential Lookup
|
28
|
+
|
29
|
+
The google-shopping-merchant-conversions-v1beta library provides several mechanisms to configure your system.
|
30
|
+
Generally, using Application Default Credentials to facilitate automatic
|
31
|
+
credentials discovery is the easist method. But if you need to explicitly specify
|
32
|
+
credentials, there are several methods available to you.
|
33
|
+
|
34
|
+
Credentials are accepted in the following ways, in the following order or precedence:
|
35
|
+
|
36
|
+
1. Credentials specified in method arguments
|
37
|
+
2. Credentials specified in configuration
|
38
|
+
3. Credentials pointed to or included in environment variables
|
39
|
+
4. Credentials found in local ADC file
|
40
|
+
5. Credentials returned by the metadata server for the attached service account (GCP)
|
41
|
+
|
42
|
+
### Configuration
|
43
|
+
|
44
|
+
You can configure a path to a JSON credentials file, either for an individual client object or
|
45
|
+
globally, for all client objects. The JSON file can contain credentials created for
|
46
|
+
[workload identity federation](https://cloud.google.com/iam/docs/workload-identity-federation),
|
47
|
+
[workforce identity federation](https://cloud.google.com/iam/docs/workforce-identity-federation), or a
|
48
|
+
[service account key](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-key).
|
49
|
+
|
50
|
+
Note: Service account keys are a security risk if not managed correctly. You should
|
51
|
+
[choose a more secure alternative to service account keys](https://cloud.google.com/docs/authentication#auth-decision-tree)
|
52
|
+
whenever possible.
|
53
|
+
|
54
|
+
To configure a credentials file for an individual client initialization:
|
55
|
+
|
56
|
+
```ruby
|
57
|
+
require "google/shopping/merchant/conversions/v1beta"
|
58
|
+
|
59
|
+
client = ::Google::Shopping::Merchant::Conversions::V1beta::ConversionSourcesService::Client.new do |config|
|
60
|
+
config.credentials = "path/to/credentialfile.json"
|
61
|
+
end
|
62
|
+
```
|
63
|
+
|
64
|
+
To configure a credentials file globally for all clients:
|
65
|
+
|
66
|
+
```ruby
|
67
|
+
require "google/shopping/merchant/conversions/v1beta"
|
68
|
+
|
69
|
+
::Google::Shopping::Merchant::Conversions::V1beta::ConversionSourcesService::Client.configure do |config|
|
70
|
+
config.credentials = "path/to/credentialfile.json"
|
71
|
+
end
|
72
|
+
|
73
|
+
client = ::Google::Shopping::Merchant::Conversions::V1beta::ConversionSourcesService::Client.new
|
74
|
+
```
|
75
|
+
|
76
|
+
### Environment Variables
|
77
|
+
|
78
|
+
You can also use an environment variable to provide a JSON credentials file.
|
79
|
+
The environment variable can contain a path to the credentials file or, for
|
80
|
+
environments such as Docker containers where writing files is not encouraged,
|
81
|
+
you can include the credentials file itself.
|
82
|
+
|
83
|
+
The JSON file can contain credentials created for
|
84
|
+
[workload identity federation](https://cloud.google.com/iam/docs/workload-identity-federation),
|
85
|
+
[workforce identity federation](https://cloud.google.com/iam/docs/workforce-identity-federation), or a
|
86
|
+
[service account key](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-key).
|
87
|
+
|
88
|
+
Note: Service account keys are a security risk if not managed correctly. You should
|
89
|
+
[choose a more secure alternative to service account keys](https://cloud.google.com/docs/authentication#auth-decision-tree)
|
90
|
+
whenever possible.
|
91
|
+
|
92
|
+
The environment variables that google-shopping-merchant-conversions-v1beta
|
93
|
+
checks for credentials are:
|
94
|
+
|
95
|
+
* `GOOGLE_CLOUD_CREDENTIALS` - Path to JSON file, or JSON contents
|
96
|
+
* `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file
|
97
|
+
|
98
|
+
```ruby
|
99
|
+
require "google/shopping/merchant/conversions/v1beta"
|
100
|
+
|
101
|
+
ENV["GOOGLE_APPLICATION_CREDENTIALS"] = "path/to/credentialfile.json"
|
102
|
+
|
103
|
+
client = ::Google::Shopping::Merchant::Conversions::V1beta::ConversionSourcesService::Client.new
|
104
|
+
```
|
105
|
+
|
106
|
+
### Local ADC file
|
107
|
+
|
108
|
+
You can set up a local ADC file with your user credentials for authentication during
|
109
|
+
development. If credentials are not provided in code or in environment variables,
|
110
|
+
then the local ADC credentials are discovered.
|
111
|
+
|
112
|
+
Follow the steps in [Quickstart](#quickstart) to set up a local ADC file.
|
113
|
+
|
114
|
+
### Google Cloud Platform environments
|
115
|
+
|
116
|
+
When running on Google Cloud Platform (GCP), including Google Compute Engine
|
117
|
+
(GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud
|
118
|
+
Functions (GCF) and Cloud Run, credentials are retrieved from the attached
|
119
|
+
service account automatically. Code should be written as if already authenticated.
|
120
|
+
|
121
|
+
For more information, see
|
122
|
+
[Set up ADC for Google Cloud services](https://cloud.google.com/docs/authentication/provide-credentials-adc#attached-sa).
|
data/README.md
CHANGED
@@ -1,8 +1,143 @@
|
|
1
|
-
#
|
2
|
-
|
3
|
-
|
4
|
-
|
5
|
-
|
6
|
-
|
7
|
-
|
8
|
-
|
1
|
+
# Ruby Client for the Merchant V1BETA API
|
2
|
+
|
3
|
+
Programmatically manage your Merchant Center accounts.
|
4
|
+
|
5
|
+
|
6
|
+
https://github.com/googleapis/google-cloud-ruby
|
7
|
+
|
8
|
+
This gem is a _versioned_ client. It provides basic client classes for a
|
9
|
+
specific version of the Merchant V1BETA API. Most users should consider using
|
10
|
+
the main client gem,
|
11
|
+
[google-shopping-merchant-conversions](https://rubygems.org/gems/google-shopping-merchant-conversions).
|
12
|
+
See the section below titled *Which client should I use?* for more information.
|
13
|
+
|
14
|
+
## Installation
|
15
|
+
|
16
|
+
```
|
17
|
+
$ gem install google-shopping-merchant-conversions-v1beta
|
18
|
+
```
|
19
|
+
|
20
|
+
## Before You Begin
|
21
|
+
|
22
|
+
In order to use this library, you first need to go through the following steps:
|
23
|
+
|
24
|
+
1. [Select or create a Cloud Platform project.](https://console.cloud.google.com/project)
|
25
|
+
1. [Enable billing for your project.](https://cloud.google.com/billing/docs/how-to/modify-project#enable_billing_for_a_project)
|
26
|
+
1. [Enable the API.](https://console.cloud.google.com/apis/library/merchantapi.googleapis.com)
|
27
|
+
1. {file:AUTHENTICATION.md Set up authentication.}
|
28
|
+
|
29
|
+
## Quick Start
|
30
|
+
|
31
|
+
```ruby
|
32
|
+
require "google/shopping/merchant/conversions/v1beta"
|
33
|
+
|
34
|
+
client = ::Google::Shopping::Merchant::Conversions::V1beta::ConversionSourcesService::Client.new
|
35
|
+
request = ::Google::Shopping::Merchant::Conversions::V1beta::CreateConversionSourceRequest.new # (request fields as keyword arguments...)
|
36
|
+
response = client.create_conversion_source request
|
37
|
+
```
|
38
|
+
|
39
|
+
View the [Client Library Documentation](https://rubydoc.info/gems/google-shopping-merchant-conversions-v1beta)
|
40
|
+
for class and method documentation.
|
41
|
+
|
42
|
+
See also the [Product Documentation](https://developers.google.com/merchant/api)
|
43
|
+
for general usage information.
|
44
|
+
|
45
|
+
## Enabling Logging
|
46
|
+
|
47
|
+
To enable logging for this library, set the logger for the underlying [gRPC](https://github.com/grpc/grpc/tree/master/src/ruby) library.
|
48
|
+
The logger that you set may be a Ruby stdlib [`Logger`](https://ruby-doc.org/current/stdlibs/logger/Logger.html) as shown below,
|
49
|
+
or a [`Google::Cloud::Logging::Logger`](https://cloud.google.com/ruby/docs/reference/google-cloud-logging/latest)
|
50
|
+
that will write logs to [Cloud Logging](https://cloud.google.com/logging/). See [grpc/logconfig.rb](https://github.com/grpc/grpc/blob/master/src/ruby/lib/grpc/logconfig.rb)
|
51
|
+
and the gRPC [spec_helper.rb](https://github.com/grpc/grpc/blob/master/src/ruby/spec/spec_helper.rb) for additional information.
|
52
|
+
|
53
|
+
Configuring a Ruby stdlib logger:
|
54
|
+
|
55
|
+
```ruby
|
56
|
+
require "logger"
|
57
|
+
|
58
|
+
module MyLogger
|
59
|
+
LOGGER = Logger.new $stderr, level: Logger::WARN
|
60
|
+
def logger
|
61
|
+
LOGGER
|
62
|
+
end
|
63
|
+
end
|
64
|
+
|
65
|
+
# Define a gRPC module-level logger method before grpc/logconfig.rb loads.
|
66
|
+
module GRPC
|
67
|
+
extend MyLogger
|
68
|
+
end
|
69
|
+
```
|
70
|
+
|
71
|
+
|
72
|
+
## Google Cloud Samples
|
73
|
+
|
74
|
+
To browse ready to use code samples check [Google Cloud Samples](https://cloud.google.com/docs/samples).
|
75
|
+
|
76
|
+
## Supported Ruby Versions
|
77
|
+
|
78
|
+
This library is supported on Ruby 2.7+.
|
79
|
+
|
80
|
+
Google provides official support for Ruby versions that are actively supported
|
81
|
+
by Ruby Core—that is, Ruby versions that are either in normal maintenance or
|
82
|
+
in security maintenance, and not end of life. Older versions of Ruby _may_
|
83
|
+
still work, but are unsupported and not recommended. See
|
84
|
+
https://www.ruby-lang.org/en/downloads/branches/ for details about the Ruby
|
85
|
+
support schedule.
|
86
|
+
|
87
|
+
## Which client should I use?
|
88
|
+
|
89
|
+
Most modern Ruby client libraries for Google APIs come in two flavors: the main
|
90
|
+
client library with a name such as `google-shopping-merchant-conversions`,
|
91
|
+
and lower-level _versioned_ client libraries with names such as
|
92
|
+
`google-shopping-merchant-conversions-v1beta`.
|
93
|
+
_In most cases, you should install the main client._
|
94
|
+
|
95
|
+
### What's the difference between the main client and a versioned client?
|
96
|
+
|
97
|
+
A _versioned client_ provides a basic set of data types and client classes for
|
98
|
+
a _single version_ of a specific service. (That is, for a service with multiple
|
99
|
+
versions, there might be a separate versioned client for each service version.)
|
100
|
+
Most versioned clients are written and maintained by a code generator.
|
101
|
+
|
102
|
+
The _main client_ is designed to provide you with the _recommended_ client
|
103
|
+
interfaces for the service. There will be only one main client for any given
|
104
|
+
service, even a service with multiple versions. The main client includes
|
105
|
+
factory methods for constructing the client objects we recommend for most
|
106
|
+
users. In some cases, those will be classes provided by an underlying versioned
|
107
|
+
client; in other cases, they will be handwritten higher-level client objects
|
108
|
+
with additional capabilities, convenience methods, or best practices built in.
|
109
|
+
Generally, the main client will default to a recommended service version,
|
110
|
+
although in some cases you can override this if you need to talk to a specific
|
111
|
+
service version.
|
112
|
+
|
113
|
+
### Why would I want to use the main client?
|
114
|
+
|
115
|
+
We recommend that most users install the main client gem for a service. You can
|
116
|
+
identify this gem as the one _without_ a version in its name, e.g.
|
117
|
+
`google-shopping-merchant-conversions`.
|
118
|
+
The main client is recommended because it will embody the best practices for
|
119
|
+
accessing the service, and may also provide more convenient interfaces or
|
120
|
+
tighter integration into frameworks and third-party libraries. In addition, the
|
121
|
+
documentation and samples published by Google will generally demonstrate use of
|
122
|
+
the main client.
|
123
|
+
|
124
|
+
### Why would I want to use a versioned client?
|
125
|
+
|
126
|
+
You can use a versioned client if you are content with a possibly lower-level
|
127
|
+
class interface, you explicitly want to avoid features provided by the main
|
128
|
+
client, or you want to access a specific service version not be covered by the
|
129
|
+
main client. You can identify versioned client gems because the service version
|
130
|
+
is part of the name, e.g. `google-shopping-merchant-conversions-v1beta`.
|
131
|
+
|
132
|
+
### What about the google-apis-<name> clients?
|
133
|
+
|
134
|
+
Client library gems with names that begin with `google-apis-` are based on an
|
135
|
+
older code generation technology. They talk to a REST/JSON backend (whereas
|
136
|
+
most modern clients talk to a [gRPC](https://grpc.io/) backend) and they may
|
137
|
+
not offer the same performance, features, and ease of use provided by more
|
138
|
+
modern clients.
|
139
|
+
|
140
|
+
The `google-apis-` clients have wide coverage across Google services, so you
|
141
|
+
might need to use one if there is no modern client available for the service.
|
142
|
+
However, if a modern client is available, we generally recommend it over the
|
143
|
+
older `google-apis-` clients.
|