google-cloud-recaptcha_enterprise 0.6.0 → 1.1.3

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 9f02d1f54e681af96c7e5e12bb610faec7d040c3da9fc48c72ff4aa46e6aab3c
4
- data.tar.gz: 61868cbf57254ee775a36728b10443441cbd58bb8f613092febbfda1c21aec2d
3
+ metadata.gz: d48b7e27a72bf0ecd171ea3520f37574bae12985801212af2b6ee07a36114f3c
4
+ data.tar.gz: 527b4976a346641e0521af88ed11661b9f1ff066937a548ba5300589fff892c9
5
5
  SHA512:
6
- metadata.gz: dc9e353eff517fed8f346a96c98ebe36027361e959b86eb5c90eeec8cdca9c8149143618db2a282ba6d61db9b9e8babcbeb94daf91b1128bf7ca63e909e3d07c
7
- data.tar.gz: 1aae8a20a106086ffb2aad01503db8a18c21c1304e8a3717ca4ec3a770812505ebd25bcb05374e01fb806514a7eae5bc0290e81572a056d2f0b0172dd603566b
6
+ metadata.gz: e00fbaa07d318f63ae5393aaf4ff2dda720fbeddb8c537b37d36e61533a0c04448a266918af90084dcce33f8c34e0d326937597223209cf059c0d1c8848aafaf
7
+ data.tar.gz: 7ca91c336b2018138bbb171f451b948317e837b41a97c3211f2bdcb35c632ce67080d43438236283b09c64b4af9cf0439173c535c5c207fe22999d2b372174d5
data/.yardopts CHANGED
@@ -8,4 +8,5 @@
8
8
  -
9
9
  README.md
10
10
  AUTHENTICATION.md
11
- LICENSE
11
+ MIGRATING.md
12
+ LICENSE.md
data/AUTHENTICATION.md CHANGED
@@ -1,16 +1,17 @@
1
1
  # Authentication
2
2
 
3
- In general, the google-cloud-recaptcha_enterprise library uses [Service
4
- Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
5
- credentials to connect to Google Cloud services. When running within [Google
6
- Cloud Platform environments](#google-cloud-platform-environments)
7
- the credentials will be discovered automatically. When running on other
3
+ In general, the google-cloud-recaptcha_enterprise library uses
4
+ [Service Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
5
+ credentials to connect to Google Cloud services. When running within
6
+ [Google Cloud Platform environments](#google-cloud-platform-environments) the
7
+ credentials will be discovered automatically. When running on other
8
8
  environments, the Service Account credentials can be specified by providing the
9
- path to the [JSON
10
- keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys) for
11
- the account (or the JSON itself) in [environment
12
- variables](#environment-variables). Additionally, Cloud SDK credentials can also
13
- be discovered automatically, but this is only recommended during development.
9
+ path to the
10
+ [JSON keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys)
11
+ for the account (or the JSON itself) in
12
+ [environment variables](#environment-variables). Additionally, Cloud SDK
13
+ credentials can also be discovered automatically, but this is only recommended
14
+ during development.
14
15
 
15
16
  ## Quickstart
16
17
 
@@ -18,7 +19,7 @@ be discovered automatically, but this is only recommended during development.
18
19
  2. Set the [environment variable](#environment-variables).
19
20
 
20
21
  ```sh
21
- export RECAPTCHA_ENTERPRISE_CREDENTIALS=/path/to/json`
22
+ export RECAPTCHA_ENTERPRISE_CREDENTIALS=path/to/keyfile.json
22
23
  ```
23
24
 
24
25
  3. Initialize the client.
@@ -26,23 +27,14 @@ export RECAPTCHA_ENTERPRISE_CREDENTIALS=/path/to/json`
26
27
  ```ruby
27
28
  require "google/cloud/recaptcha_enterprise"
28
29
 
29
- client = Google::Cloud::RecaptchaEnterprise.new
30
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service
30
31
  ```
31
32
 
32
- ## Project and Credential Lookup
33
+ ## Credential Lookup
33
34
 
34
35
  The google-cloud-recaptcha_enterprise library aims to make authentication
35
36
  as simple as possible, and provides several mechanisms to configure your system
36
- without providing **Project ID** and **Service Account Credentials** directly in
37
- code.
38
-
39
- **Project ID** is discovered in the following order:
40
-
41
- 1. Specify project ID in method arguments
42
- 2. Specify project ID in configuration
43
- 3. Discover project ID in environment variables
44
- 4. Discover GCP project ID
45
- 5. Discover project ID in credentials JSON
37
+ without requiring **Service Account Credentials** directly in code.
46
38
 
47
39
  **Credentials** are discovered in the following order:
48
40
 
@@ -55,28 +47,24 @@ code.
55
47
 
56
48
  ### Google Cloud Platform environments
57
49
 
58
- When running on Google Cloud Platform (GCP), including Google Compute Engine (GCE),
59
- Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud Functions
60
- (GCF) and Cloud Run, the **Project ID** and **Credentials** and are discovered
61
- automatically. Code should be written as if already authenticated.
50
+ When running on Google Cloud Platform (GCP), including Google Compute Engine
51
+ (GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud
52
+ Functions (GCF) and Cloud Run, **Credentials** are discovered automatically.
53
+ Code should be written as if already authenticated.
62
54
 
63
55
  ### Environment Variables
64
56
 
65
- The **Project ID** and **Credentials JSON** can be placed in environment
66
- variables instead of declaring them directly in code. Each service has its own
67
- environment variable, allowing for different service accounts to be used for
68
- different services. (See the READMEs for the individual service gems for
69
- details.) The path to the **Credentials JSON** file can be stored in the
70
- environment variable, or the **Credentials JSON** itself can be stored for
71
- environments such as Docker containers where writing files is difficult or not
72
- encouraged.
73
-
74
- The environment variables that google-cloud-recaptcha_enterprise checks for project ID are:
57
+ The **Credentials JSON** can be placed in environment variables instead of
58
+ declaring them directly in code. Each service has its own environment variable,
59
+ allowing for different service accounts to be used for different services. (See
60
+ the READMEs for the individual service gems for details.) The path to the
61
+ **Credentials JSON** file can be stored in the environment variable, or the
62
+ **Credentials JSON** itself can be stored for environments such as Docker
63
+ containers where writing files is difficult or not encouraged.
75
64
 
76
- 1. `RECAPTCHA_ENTERPRISE_PROJECT`
77
- 2. `GOOGLE_CLOUD_PROJECT`
78
-
79
- The environment variables that google-cloud-recaptcha_enterprise checks for credentials are configured on {Google::Cloud::RecaptchaEnterprise::V1beta1::Credentials}:
65
+ The environment variables that google-cloud-recaptcha_enterprise
66
+ checks for credentials are configured on the service Credentials class (such as
67
+ `::Google::Cloud::RecaptchaEnterprise::V1::RecaptchaEnterpriseService::Credentials`):
80
68
 
81
69
  1. `RECAPTCHA_ENTERPRISE_CREDENTIALS` - Path to JSON file, or JSON contents
82
70
  2. `RECAPTCHA_ENTERPRISE_KEYFILE` - Path to JSON file, or JSON contents
@@ -87,25 +75,34 @@ The environment variables that google-cloud-recaptcha_enterprise checks for cred
87
75
  ```ruby
88
76
  require "google/cloud/recaptcha_enterprise"
89
77
 
90
- ENV["RECAPTCHA_ENTERPRISE_PROJECT"] = "my-project-id"
91
78
  ENV["RECAPTCHA_ENTERPRISE_CREDENTIALS"] = "path/to/keyfile.json"
92
79
 
93
- client = Google::Cloud::RecaptchaEnterprise.new
80
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service
94
81
  ```
95
82
 
96
83
  ### Configuration
97
84
 
98
- The **Project ID** and **Credentials JSON** can be configured instead of placing them in environment variables or providing them as arguments.
85
+ The **Credentials JSON** can be configured instead of placing them in
86
+ environment variables. Either on an individual client initialization:
87
+
88
+ ```ruby
89
+ require "google/cloud/recaptcha_enterprise"
90
+
91
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service do |config|
92
+ config.credentials = "path/to/keyfile.json"
93
+ end
94
+ ```
95
+
96
+ Or configured globally for all clients:
99
97
 
100
98
  ```ruby
101
99
  require "google/cloud/recaptcha_enterprise"
102
100
 
103
101
  Google::Cloud::RecaptchaEnterprise.configure do |config|
104
- config.project_id = "my-project-id"
105
102
  config.credentials = "path/to/keyfile.json"
106
103
  end
107
104
 
108
- client = Google::Cloud::RecaptchaEnterprise.new
105
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service
109
106
  ```
110
107
 
111
108
  ### Cloud SDK
@@ -134,24 +131,24 @@ To configure your system for this, simply:
134
131
 
135
132
  ## Creating a Service Account
136
133
 
137
- Google Cloud requires a **Project ID** and **Service Account Credentials** to
138
- connect to the APIs. You will use the **Project ID** and **JSON key file** to
134
+ Google Cloud requires **Service Account Credentials** to
135
+ connect to the APIs. You will use the **JSON key file** to
139
136
  connect to most services with google-cloud-recaptcha_enterprise.
140
137
 
141
- If you are not running this client within [Google Cloud Platform
142
- environments](#google-cloud-platform-environments), you need a Google
143
- Developers service account.
138
+ If you are not running this client within
139
+ [Google Cloud Platform environments](#google-cloud-platform-environments), you
140
+ need a Google Developers service account.
144
141
 
145
142
  1. Visit the [Google Developers Console][dev-console].
146
- 1. Create a new project or click on an existing project.
147
- 1. Activate the slide-out navigation tray and select **API Manager**. From
143
+ 2. Create a new project or click on an existing project.
144
+ 3. Activate the slide-out navigation tray and select **API Manager**. From
148
145
  here, you will enable the APIs that your application requires.
149
146
 
150
147
  ![Enable the APIs that your application requires][enable-apis]
151
148
 
152
149
  *Note: You may need to enable billing in order to use these services.*
153
150
 
154
- 1. Select **Credentials** from the side navigation.
151
+ 4. Select **Credentials** from the side navigation.
155
152
 
156
153
  You should see a screen like one of the following.
157
154
 
data/LICENSE.md ADDED
@@ -0,0 +1,203 @@
1
+ Apache License
2
+ ==============
3
+
4
+ * Version 2.0, January 2004
5
+ * https://www.apache.org/licenses/
6
+
7
+ ### TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
8
+
9
+ 1. **Definitions.**
10
+
11
+ "License" shall mean the terms and conditions for use, reproduction,
12
+ and distribution as defined by Sections 1 through 9 of this document.
13
+
14
+ "Licensor" shall mean the copyright owner or entity authorized by
15
+ the copyright owner that is granting the License.
16
+
17
+ "Legal Entity" shall mean the union of the acting entity and all
18
+ other entities that control, are controlled by, or are under common
19
+ control with that entity. For the purposes of this definition,
20
+ "control" means (i) the power, direct or indirect, to cause the
21
+ direction or management of such entity, whether by contract or
22
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
23
+ outstanding shares, or (iii) beneficial ownership of such entity.
24
+
25
+ "You" (or "Your") shall mean an individual or Legal Entity
26
+ exercising permissions granted by this License.
27
+
28
+ "Source" form shall mean the preferred form for making modifications,
29
+ including but not limited to software source code, documentation
30
+ source, and configuration files.
31
+
32
+ "Object" form shall mean any form resulting from mechanical
33
+ transformation or translation of a Source form, including but
34
+ not limited to compiled object code, generated documentation,
35
+ and conversions to other media types.
36
+
37
+ "Work" shall mean the work of authorship, whether in Source or
38
+ Object form, made available under the License, as indicated by a
39
+ copyright notice that is included in or attached to the work
40
+ (an example is provided in the Appendix below).
41
+
42
+ "Derivative Works" shall mean any work, whether in Source or Object
43
+ form, that is based on (or derived from) the Work and for which the
44
+ editorial revisions, annotations, elaborations, or other modifications
45
+ represent, as a whole, an original work of authorship. For the purposes
46
+ of this License, Derivative Works shall not include works that remain
47
+ separable from, or merely link (or bind by name) to the interfaces of,
48
+ the Work and Derivative Works thereof.
49
+
50
+ "Contribution" shall mean any work of authorship, including
51
+ the original version of the Work and any modifications or additions
52
+ to that Work or Derivative Works thereof, that is intentionally
53
+ submitted to Licensor for inclusion in the Work by the copyright owner
54
+ or by an individual or Legal Entity authorized to submit on behalf of
55
+ the copyright owner. For the purposes of this definition, "submitted"
56
+ means any form of electronic, verbal, or written communication sent
57
+ to the Licensor or its representatives, including but not limited to
58
+ communication on electronic mailing lists, source code control systems,
59
+ and issue tracking systems that are managed by, or on behalf of, the
60
+ Licensor for the purpose of discussing and improving the Work, but
61
+ excluding communication that is conspicuously marked or otherwise
62
+ designated in writing by the copyright owner as "Not a Contribution."
63
+
64
+ "Contributor" shall mean Licensor and any individual or Legal Entity
65
+ on behalf of whom a Contribution has been received by Licensor and
66
+ subsequently incorporated within the Work.
67
+
68
+ 2. **Grant of Copyright License.** Subject to the terms and conditions of
69
+ this License, each Contributor hereby grants to You a perpetual,
70
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
71
+ copyright license to reproduce, prepare Derivative Works of,
72
+ publicly display, publicly perform, sublicense, and distribute the
73
+ Work and such Derivative Works in Source or Object form.
74
+
75
+ 3. **Grant of Patent License.** Subject to the terms and conditions of
76
+ this License, each Contributor hereby grants to You a perpetual,
77
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
78
+ (except as stated in this section) patent license to make, have made,
79
+ use, offer to sell, sell, import, and otherwise transfer the Work,
80
+ where such license applies only to those patent claims licensable
81
+ by such Contributor that are necessarily infringed by their
82
+ Contribution(s) alone or by combination of their Contribution(s)
83
+ with the Work to which such Contribution(s) was submitted. If You
84
+ institute patent litigation against any entity (including a
85
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
86
+ or a Contribution incorporated within the Work constitutes direct
87
+ or contributory patent infringement, then any patent licenses
88
+ granted to You under this License for that Work shall terminate
89
+ as of the date such litigation is filed.
90
+
91
+ 4. **Redistribution.** You may reproduce and distribute copies of the
92
+ Work or Derivative Works thereof in any medium, with or without
93
+ modifications, and in Source or Object form, provided that You
94
+ meet the following conditions:
95
+
96
+ * **(a)** You must give any other recipients of the Work or
97
+ Derivative Works a copy of this License; and
98
+
99
+ * **(b)** You must cause any modified files to carry prominent notices
100
+ stating that You changed the files; and
101
+
102
+ * **(c)** You must retain, in the Source form of any Derivative Works
103
+ that You distribute, all copyright, patent, trademark, and
104
+ attribution notices from the Source form of the Work,
105
+ excluding those notices that do not pertain to any part of
106
+ the Derivative Works; and
107
+
108
+ * **(d)** If the Work includes a "NOTICE" text file as part of its
109
+ distribution, then any Derivative Works that You distribute must
110
+ include a readable copy of the attribution notices contained
111
+ within such NOTICE file, excluding those notices that do not
112
+ pertain to any part of the Derivative Works, in at least one
113
+ of the following places: within a NOTICE text file distributed
114
+ as part of the Derivative Works; within the Source form or
115
+ documentation, if provided along with the Derivative Works; or,
116
+ within a display generated by the Derivative Works, if and
117
+ wherever such third-party notices normally appear. The contents
118
+ of the NOTICE file are for informational purposes only and
119
+ do not modify the License. You may add Your own attribution
120
+ notices within Derivative Works that You distribute, alongside
121
+ or as an addendum to the NOTICE text from the Work, provided
122
+ that such additional attribution notices cannot be construed
123
+ as modifying the License.
124
+
125
+ You may add Your own copyright statement to Your modifications and
126
+ may provide additional or different license terms and conditions
127
+ for use, reproduction, or distribution of Your modifications, or
128
+ for any such Derivative Works as a whole, provided Your use,
129
+ reproduction, and distribution of the Work otherwise complies with
130
+ the conditions stated in this License.
131
+
132
+ 5. **Submission of Contributions.** Unless You explicitly state otherwise,
133
+ any Contribution intentionally submitted for inclusion in the Work
134
+ by You to the Licensor shall be under the terms and conditions of
135
+ this License, without any additional terms or conditions.
136
+ Notwithstanding the above, nothing herein shall supersede or modify
137
+ the terms of any separate license agreement you may have executed
138
+ with Licensor regarding such Contributions.
139
+
140
+ 6. **Trademarks.** This License does not grant permission to use the trade
141
+ names, trademarks, service marks, or product names of the Licensor,
142
+ except as required for reasonable and customary use in describing the
143
+ origin of the Work and reproducing the content of the NOTICE file.
144
+
145
+ 7. **Disclaimer of Warranty.** Unless required by applicable law or
146
+ agreed to in writing, Licensor provides the Work (and each
147
+ Contributor provides its Contributions) on an "AS IS" BASIS,
148
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
149
+ implied, including, without limitation, any warranties or conditions
150
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
151
+ PARTICULAR PURPOSE. You are solely responsible for determining the
152
+ appropriateness of using or redistributing the Work and assume any
153
+ risks associated with Your exercise of permissions under this License.
154
+
155
+ 8. **Limitation of Liability.** In no event and under no legal theory,
156
+ whether in tort (including negligence), contract, or otherwise,
157
+ unless required by applicable law (such as deliberate and grossly
158
+ negligent acts) or agreed to in writing, shall any Contributor be
159
+ liable to You for damages, including any direct, indirect, special,
160
+ incidental, or consequential damages of any character arising as a
161
+ result of this License or out of the use or inability to use the
162
+ Work (including but not limited to damages for loss of goodwill,
163
+ work stoppage, computer failure or malfunction, or any and all
164
+ other commercial damages or losses), even if such Contributor
165
+ has been advised of the possibility of such damages.
166
+
167
+ 9. **Accepting Warranty or Additional Liability.** While redistributing
168
+ the Work or Derivative Works thereof, You may choose to offer,
169
+ and charge a fee for, acceptance of support, warranty, indemnity,
170
+ or other liability obligations and/or rights consistent with this
171
+ License. However, in accepting such obligations, You may act only
172
+ on Your own behalf and on Your sole responsibility, not on behalf
173
+ of any other Contributor, and only if You agree to indemnify,
174
+ defend, and hold each Contributor harmless for any liability
175
+ incurred by, or claims asserted against, such Contributor by reason
176
+ of your accepting any such warranty or additional liability.
177
+
178
+ _END OF TERMS AND CONDITIONS_
179
+
180
+ ### APPENDIX: How to apply the Apache License to your work.
181
+
182
+ To apply the Apache License to your work, attach the following
183
+ boilerplate notice, with the fields enclosed by brackets "`[]`"
184
+ replaced with your own identifying information. (Don't include
185
+ the brackets!) The text should be enclosed in the appropriate
186
+ comment syntax for the file format. We also recommend that a
187
+ file or class name and description of purpose be included on the
188
+ same "printed page" as the copyright notice for easier
189
+ identification within third-party archives.
190
+
191
+ Copyright [yyyy] [name of copyright owner]
192
+
193
+ Licensed under the Apache License, Version 2.0 (the "License");
194
+ you may not use this file except in compliance with the License.
195
+ You may obtain a copy of the License at
196
+
197
+ https://www.apache.org/licenses/LICENSE-2.0
198
+
199
+ Unless required by applicable law or agreed to in writing, software
200
+ distributed under the License is distributed on an "AS IS" BASIS,
201
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
202
+ See the License for the specific language governing permissions and
203
+ limitations under the License.
data/MIGRATING.md ADDED
@@ -0,0 +1,329 @@
1
+ ## Migrating to google-cloud-recaptcha_enterprise 1.0
2
+
3
+ The 1.0 release of the google-cloud-recaptcha_enterprise client is a significant upgrade
4
+ based on a [next-gen code generator](https://github.com/googleapis/gapic-generator-ruby),
5
+ and includes substantial interface changes. Existing code written for earlier
6
+ versions of this library will likely require updates to use this version.
7
+ This document describes the changes that have been made, and what you need to
8
+ do to update your usage.
9
+
10
+ To summarize:
11
+
12
+ * The 1.0 release supports versions V1 and V1beta1 of the reCAPTCHA
13
+ Enterprise service. Earlier releases supported only V1beta1.
14
+ * The library has been broken out into multiple libraries. The new gems
15
+ `google-cloud-recaptcha_enterprise-v1` and `google-cloud-recaptcha_enterprise-v1beta1` contain the
16
+ actual client classes for versions V1 and V1beta1 of the reCAPTCHA Enterprise service,
17
+ and the gem `google-cloud-recaptcha_enterprise` now simply provides a convenience wrapper.
18
+ See [Library Structure](#library-structure) for more info.
19
+ * The library uses a new configuration mechanism giving you closer control
20
+ over endpoint address, network timeouts, and retry. See
21
+ [Client Configuration](#client-configuration) for more info. Furthermore,
22
+ when creating a client object, you can customize its configuration in a
23
+ block rather than passing arguments to the constructor. See
24
+ [Creating Clients](#creating-clients) for more info.
25
+ * Previously, positional arguments were used to indicate required arguments.
26
+ Now, all method arguments are keyword arguments, with documentation that
27
+ specifies whether they are required or optional. Additionally, you can pass
28
+ a proto request object instead of separate arguments. See
29
+ [Passing Arguments](#passing-arguments) for more info.
30
+ * Previously, some client classes included helper methods for constructing
31
+ resource paths. These methods now take keyword rather than positional
32
+ arguments, and are also available in a separate paths module. See
33
+ [Resource Path Helpers](#resource-path-helpers) for more info.
34
+ * Previously, clients reported RPC errors by raising instances of
35
+ `Google::Gax::GaxError` and its subclasses. Now, RPC exceptions are of type
36
+ `Google::Cloud::Error` and its subclasses. See
37
+ [Handling Errors](#handling-errors) for more info.
38
+ * Some classes have moved into different namespaces. In particular, classes
39
+ that were under `Google::Cloud::Recaptchaenterprise` were moved under
40
+ `Google::Cloud::RecaptchaEnterprise`. See
41
+ [Class Namespaces](#class-namespaces) for more info.
42
+
43
+ ### Library Structure
44
+
45
+ Older 0.x releases of the `google-cloud-recaptcha_enterprise` gem were all-in-one gems
46
+ that included potentially multiple clients for multiple versions of the
47
+ reCAPTCHA Enterprise service. The `Google::Cloud::RecaptchaEnterprise.new` factory method would
48
+ return you an instance of a `Google::Cloud::RecaptchaEnterprise::V1beta1::RecaptchaEnterpriseClient`
49
+ object for the V1beta1 version of the service. (Version V1 of the service was
50
+ not supported by 0.x releases.) All these classes were defined in the same gem.
51
+
52
+ With the 1.0 release, the `google-cloud-recaptcha_enterprise` gem still provides factory
53
+ methods for obtaining clients. (The method signatures will have changed. See
54
+ [Creating Clients](#creating-clients) for details.) However, the actual client
55
+ classes have been moved into separate gems, one per service version. The
56
+ `Google::Cloud::RecaptchaEnterprise::V1::RecaptchaEnterpriseService::Client` class, along with its
57
+ helpers and data types, is now part of the `google-cloud-recaptcha_enterprise-v1` gem.
58
+ Similarly, the `Google::Cloud::RecaptchaEnterprise::V1beta1::RecaptchaEnterpriseService::Client`
59
+ class is part of the `google-cloud-recaptcha_enterprise-v1beta1` gem.
60
+
61
+ For normal usage, you can continue to install the `google-cloud-recaptcha_enterprise` gem
62
+ (which will bring in the versioned client gems as dependencies) and continue to
63
+ use factory methods to create clients. However, you may alternatively choose to
64
+ install only one of the versioned gems. For example, if you know you will only
65
+ use `V1` of the service, you can install `google-cloud-recaptcha_enterprise-v1` by
66
+ itself, and construct instances of the
67
+ `Google::Cloud::RecaptchaEnterprise::V1::RecaptchaEnterpriseService::Client` client class directly.
68
+
69
+ ### Client Configuration
70
+
71
+ In older releases, if you wanted to customize performance parameters or
72
+ low-level behavior of the client (such as credentials, timeouts, or
73
+ instrumentation), you would pass a variety of keyword arguments to the client
74
+ constructor. It was also extremely difficult to customize the default settings.
75
+
76
+ With the 1.0 release, a configuration interface provides control over these
77
+ parameters, including defaults for all instances of a client, and settings for
78
+ each specific client instance. For example, to set default credentials and
79
+ timeout for all reCAPTCHA Enterprise V1 clients:
80
+
81
+ ```
82
+ Google::Cloud::RecaptchaEnterprise::V1::RecaptchaEnterpriseService::Client.configure do |config|
83
+ config.credentials = "/path/to/credentials.json"
84
+ config.timeout = 10.0
85
+ end
86
+ ```
87
+
88
+ Individual RPCs can also be configured independently. For example, to set the
89
+ timeout for the `create_assessment` call:
90
+
91
+ ```
92
+ Google::Cloud::RecaptchaEnterprise::V1::RecaptchaEnterpriseService::Client.configure do |config|
93
+ config.rpcs.create_assessment.timeout = 20.0
94
+ end
95
+ ```
96
+
97
+ Defaults for certain configurations can be set for all reCAPTCHA Enterprise versions and
98
+ services globally:
99
+
100
+ ```
101
+ Google::Cloud::RecaptchaEnterprise.configure do |config|
102
+ config.credentials = "/path/to/credentials.json"
103
+ config.timeout = 10.0
104
+ end
105
+ ```
106
+
107
+ Finally, you can override the configuration for each client instance. See the
108
+ next section on [Creating Clients](#creating-clients) for details.
109
+
110
+ ### Creating Clients
111
+
112
+ In older releases, to create a client object, you would use the
113
+ `Google::Cloud::RecaptchaEnterprise.new` class method. Keyword arguments were available to
114
+ select a service version and to configure parameters such as credentials and
115
+ timeouts.
116
+
117
+ With the 1.0 release, use the `Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service` class
118
+ method to create a client object. You may select a service version using the
119
+ `:version` keyword argument. However, other configuration parameters should be
120
+ set in a configuration block when you create the client.
121
+
122
+ Old:
123
+ ```
124
+ client = Google::Cloud::RecaptchaEnterprise.new credentials: "/path/to/credentials.json"
125
+ ```
126
+
127
+ New:
128
+ ```
129
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service do |config|
130
+ config.credentials = "/path/to/credentials.json"
131
+ end
132
+ ```
133
+
134
+ The configuration block is optional. If you do not provide it, or you do not
135
+ set some configuration parameters, then the default configuration is used. See
136
+ [Client Configuration](#client-configuration).
137
+
138
+ ### Passing Arguments
139
+
140
+ In older releases, required arguments would be passed as positional method
141
+ arguments, while most optional arguments would be passed as keyword arguments.
142
+
143
+ With the 1.0 release, all RPC arguments are passed as keyword arguments,
144
+ regardless of whether they are required or optional. For example:
145
+
146
+ Old:
147
+ ```
148
+ client = Google::Cloud::RecaptchaEnterprise.new
149
+
150
+ parent = "projects/my-project"
151
+
152
+ # Parent is a positional argument, while page_size is a keyword argument.
153
+ response = client.list_keys parent, page_size: 10
154
+ ```
155
+
156
+ New:
157
+ ```
158
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service
159
+
160
+ parent = "projects/my-project"
161
+
162
+ # Both parent and page_size are keyword arguments.
163
+ response = client.list_keys parent: parent, page_size: 10
164
+ ```
165
+
166
+ In the 1.0 release, it is also possible to pass a request object, either
167
+ as a hash or as a protocol buffer.
168
+
169
+ New:
170
+ ```
171
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service
172
+
173
+ request = Google::Cloud::RecaptchaEnterprise::V1::ListKeysRequest.new(
174
+ parent: "projects/my-project",
175
+ page_size: 10
176
+ )
177
+
178
+ # Pass a request object as a positional argument:
179
+ response = client.list_keys request
180
+ ```
181
+
182
+ Finally, in older releases, to provide call options, you would pass a
183
+ `Google::Gax::CallOptions` object with the `:options` keyword argument. In the
184
+ 1.0 release, pass call options using a _second set_ of keyword arguments.
185
+
186
+ Old:
187
+ ```
188
+ client = Google::Cloud::RecaptchaEnterprise.new
189
+
190
+ parent = "projects/my-project"
191
+
192
+ options = Google::Gax::CallOptions.new timeout: 10.0
193
+
194
+ response = client.list_keys parent, page_size: 10, options: options
195
+ ```
196
+
197
+ New:
198
+ ```
199
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service
200
+
201
+ parent = "projects/my-project"
202
+
203
+ # Use a hash to wrap the normal call arguments (or pass a request object), and
204
+ # then add further keyword arguments for the call options.
205
+ response = client.list_keys(
206
+ { parent: parent, page_size: 10 },
207
+ timeout: 10.0
208
+ )
209
+ ```
210
+
211
+ ### Resource Path Helpers
212
+
213
+ The client library includes helper methods for generating the resource path
214
+ strings passed to many calls. These helpers have changed in two ways:
215
+
216
+ * In older releases, they are both _class_ methods and _instance_ methods on
217
+ the client class. In the 1.0 release, they are _instance methods only_.
218
+ However, they are also available on a separate paths module that you can
219
+ include elsewhere for convenience.
220
+ * In older releases, arguments to a resource path helper are passed as
221
+ _positional_ arguments. In the 1.0 release, they are passed as named _keyword_
222
+ arguments.
223
+
224
+ Following is an example involving using a resource path helper.
225
+
226
+ Old:
227
+ ```
228
+ client = Google::Cloud::RecaptchaEnterprise.new
229
+
230
+ # Call the helper using positional arguments.
231
+ parent = client.project_path "my-project"
232
+
233
+ response = client.list_keys parent
234
+ ```
235
+
236
+ New:
237
+ ```
238
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service
239
+
240
+ # Call the helper using keyword arguments
241
+ parent = client.project_path project: "my-project"
242
+
243
+ response = client.list_keys parent: parent
244
+ ```
245
+
246
+ In the 1.0 client, you can also use the paths module as a convenience module.
247
+
248
+ New:
249
+ ```
250
+ # Bring the path helper methods into the current class
251
+ include Google::Cloud::RecaptchaEnterprise::V1::RecaptchaEnterpriseService::Paths
252
+
253
+ def foo
254
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service
255
+
256
+ # Call the included helper method
257
+ parent = project_path project: "my-project"
258
+
259
+ response = client.list_keys parent: parent
260
+
261
+ # Do something with response...
262
+ end
263
+ ```
264
+
265
+ ### Handling Errors
266
+
267
+ The client reports standard
268
+ [gRPC error codes](https://github.com/grpc/grpc/blob/master/doc/statuscodes.md)
269
+ by raising exceptions. In older releases, these exceptions were located in the
270
+ `Google::Gax` namespace and were subclasses of the `Google::Gax::GaxError` base
271
+ exception class, defined in the `google-gax` gem. However, these classes were
272
+ different from the standard exceptions (subclasses of `Google::Cloud::Error`)
273
+ thrown by other client libraries such as `google-cloud-storage`.
274
+
275
+ The 1.0 client library now uses the `Google::Cloud::Error` exception hierarchy,
276
+ for consistency across all the Google Cloud client libraries. In general, these
277
+ exceptions have the same name as their counterparts from older releases, but
278
+ are located in the `Google::Cloud` namespace rather than the `Google::Gax`
279
+ namespace.
280
+
281
+ Old:
282
+ ```
283
+ client = Google::Cloud::RecaptchaEnterprise.new
284
+
285
+ parent = "projects/my-project"
286
+
287
+ begin
288
+ response = client.list_keys parent, page_size: 10
289
+ rescue Google::Gax::Error => e
290
+ # Handle exceptions that subclass Google::Gax::Error
291
+ end
292
+ ```
293
+
294
+ New:
295
+ ```
296
+ client = Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service
297
+
298
+ parent = "projects/my-project"
299
+
300
+ begin
301
+ response = client.list_keys parent: parent, page_size: 10
302
+ rescue Google::Cloud::Error => e
303
+ # Handle exceptions that subclass Google::Cloud::Error
304
+ end
305
+ ```
306
+
307
+ ### Class Namespaces
308
+
309
+ In older releases, (protobuf) data type classes were located under the module
310
+ `Google::Cloud::Recaptchaenterprise` (note the lower-case "e"), even though the
311
+ client class and most other classes were under `Google::Cloud::RecaptchaEnterprise`
312
+ (with an upper-case "E"). In the 1.0 release, all classes, including data types,
313
+ are under the module `Google::Cloud::RecaptchaEnterprise`.
314
+
315
+ In older releases, the client object was of classes with names like:
316
+ `Google::Cloud::RecaptchaEnterprise::V1beta1::RecaptchaEnterpriseClient`.
317
+ In the 1.0 release, the corresponding client object is of a different class:
318
+ `Google::Cloud::RecaptchaEnterprise::V1beta1::RecaptchaEnterpriseService::Client`.
319
+ Note that most users will use the factory methods such as
320
+ `Google::Cloud::RecaptchaEnterprise.recaptcha_enterprise_service` to create instances of the client object,
321
+ so you may not need to reference the actual class directly.
322
+ See [Creating Clients](#creating-clients).
323
+
324
+ In older releases, the credentials object was of class
325
+ `Google::Cloud::RecaptchaEnterprise::V1beta1::Credentials`.
326
+ In the 1.0 release, each service has its own credentials class, e.g.
327
+ `Google::Cloud::RecaptchaEnterprise::V1beta1::RecaptchaEnterpriseService::Credentials`.
328
+ Again, most users will not need to reference this class directly.
329
+ See [Client Configuration](#client-configuration).