google-cloud-phishing_protection-v1beta1 0.1.4 → 0.2.0
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:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: b5cafe8acc4d7b787c74d23f7bee9d141590ce00d8f7ad302d4a42d54002ca09
|
4
|
+
data.tar.gz: 9f8c0d79e139451163ae53ac539e7a91429f807670d38ea4f7999eab2e58f84d
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 137d258a3d056145a3da7eec6fe2c2515eb9fcd249e252a15452dc36a0280feb0275347cd6555a572a6af8b1857abb00e72dabb9172f0322d73801604c353052
|
7
|
+
data.tar.gz: 628f5c77d96e99cec01dff0b6e367b64a4f3b084ae146ff52b95a67ef57fbce3e2708dc3d904600b4a956401dd2f154fb9a7b2171943f6ec7eab02027bdd0650
|
data/README.md
CHANGED
@@ -6,6 +6,12 @@ Phishing Protection helps prevent users from accessing phishing sites by identif
|
|
6
6
|
|
7
7
|
https://github.com/googleapis/google-cloud-ruby
|
8
8
|
|
9
|
+
This gem is a _versioned_ client. It provides basic client classes for a
|
10
|
+
specific version of the Phishing Protection V1beta1 API. Most users should consider using
|
11
|
+
the main client gem,
|
12
|
+
[google-cloud-phishing_protection](https://rubygems.org/gems/google-cloud-phishing_protection).
|
13
|
+
See the section below titled *Which client should I use?* for more information.
|
14
|
+
|
9
15
|
## Installation
|
10
16
|
|
11
17
|
```
|
@@ -73,3 +79,61 @@ in security maintenance, and not end of life. Currently, this means Ruby 2.4
|
|
73
79
|
and later. Older versions of Ruby _may_ still work, but are unsupported and not
|
74
80
|
recommended. See https://www.ruby-lang.org/en/downloads/branches/ for details
|
75
81
|
about the Ruby support schedule.
|
82
|
+
|
83
|
+
## Which client should I use?
|
84
|
+
|
85
|
+
Most modern Ruby client libraries for Google APIs come in two flavors: the main
|
86
|
+
client library with a name such as `google-cloud-phishing_protection`,
|
87
|
+
and lower-level _versioned_ client libraries with names such as
|
88
|
+
`google-cloud-phishing_protection-v1beta1`.
|
89
|
+
_In most cases, you should install the main client._
|
90
|
+
|
91
|
+
### What's the difference between the main client and a versioned client?
|
92
|
+
|
93
|
+
A _versioned client_ provides a basic set of data types and client classes for
|
94
|
+
a _single version_ of a specific service. (That is, for a service with multiple
|
95
|
+
versions, there might be a separate versioned client for each service version.)
|
96
|
+
Most versioned clients are written and maintained by a code generator.
|
97
|
+
|
98
|
+
The _main client_ is designed to provide you with the _recommended_ client
|
99
|
+
interfaces for the service. There will be only one main client for any given
|
100
|
+
service, even a service with multiple versions. The main client includes
|
101
|
+
factory methods for constructing the client objects we recommend for most
|
102
|
+
users. In some cases, those will be classes provided by an underlying versioned
|
103
|
+
client; in other cases, they will be handwritten higher-level client objects
|
104
|
+
with additional capabilities, convenience methods, or best practices built in.
|
105
|
+
Generally, the main client will default to a recommended service version,
|
106
|
+
although in some cases you can override this if you need to talk to a specific
|
107
|
+
service version.
|
108
|
+
|
109
|
+
### Why would I want to use the main client?
|
110
|
+
|
111
|
+
We recommend that most users install the main client gem for a service. You can
|
112
|
+
identify this gem as the one _without_ a version in its name, e.g.
|
113
|
+
`google-cloud-phishing_protection`.
|
114
|
+
The main client is recommended because it will embody the best practices for
|
115
|
+
accessing the service, and may also provide more convenient interfaces or
|
116
|
+
tighter integration into frameworks and third-party libraries. In addition, the
|
117
|
+
documentation and samples published by Google will generally demonstrate use of
|
118
|
+
the main client.
|
119
|
+
|
120
|
+
### Why would I want to use a versioned client?
|
121
|
+
|
122
|
+
You can use a versioned client if you are content with a possibly lower-level
|
123
|
+
class interface, you explicitly want to avoid features provided by the main
|
124
|
+
client, or you want to access a specific service version not be covered by the
|
125
|
+
main client. You can identify versioned client gems because the service version
|
126
|
+
is part of the name, e.g. `google-cloud-phishing_protection-v1beta1`.
|
127
|
+
|
128
|
+
### What about the google-apis-<name> clients?
|
129
|
+
|
130
|
+
Client library gems with names that begin with `google-apis-` are based on an
|
131
|
+
older code generation technology. They talk to a REST/JSON backend (whereas
|
132
|
+
most modern clients talk to a [gRPC](https://grpc.io/) backend) and they may
|
133
|
+
not offer the same performance, features, and ease of use provided by more
|
134
|
+
modern clients.
|
135
|
+
|
136
|
+
The `google-apis-` clients have wide coverage across Google services, so you
|
137
|
+
might need to use one if there is no modern client available for the service.
|
138
|
+
However, if a modern client is available, we generally recommend it over the
|
139
|
+
older `google-apis-` clients.
|
@@ -128,7 +128,13 @@ module Google
|
|
128
128
|
|
129
129
|
# Create credentials
|
130
130
|
credentials = @config.credentials
|
131
|
-
|
131
|
+
# Use self-signed JWT if the scope and endpoint are unchanged from default,
|
132
|
+
# but only if the default endpoint does not have a region prefix.
|
133
|
+
enable_self_signed_jwt = @config.scope == Client.configure.scope &&
|
134
|
+
@config.endpoint == Client.configure.endpoint &&
|
135
|
+
!@config.endpoint.split(".").first.include?("-")
|
136
|
+
credentials ||= Credentials.default scope: @config.scope,
|
137
|
+
enable_self_signed_jwt: enable_self_signed_jwt
|
132
138
|
if credentials.is_a?(String) || credentials.is_a?(Hash)
|
133
139
|
credentials = Credentials.new credentials, scope: @config.scope
|
134
140
|
end
|
@@ -54,6 +54,12 @@ module Google
|
|
54
54
|
# This indicates that the field may be set once in a request to create a
|
55
55
|
# resource, but may not be changed thereafter.
|
56
56
|
IMMUTABLE = 5
|
57
|
+
|
58
|
+
# Denotes that a (repeated) field is an unordered list.
|
59
|
+
# This indicates that the service may provide the elements of the list
|
60
|
+
# in any arbitrary order, rather than the order the user originally
|
61
|
+
# provided. Additionally, the list's order may or may not be stable.
|
62
|
+
UNORDERED_LIST = 6
|
57
63
|
end
|
58
64
|
end
|
59
65
|
end
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: google-cloud-phishing_protection-v1beta1
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.2.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Google LLC
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2021-
|
11
|
+
date: 2021-02-02 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: gapic-common
|
@@ -153,7 +153,10 @@ dependencies:
|
|
153
153
|
description: Phishing Protection helps prevent users from accessing phishing sites
|
154
154
|
by identifying various signals associated with malicious content, including the
|
155
155
|
use of your brand assets, classifying malicious content that uses your brand and
|
156
|
-
reporting the unsafe URLs to Google Safe Browsing.
|
156
|
+
reporting the unsafe URLs to Google Safe Browsing. Note that google-cloud-phishing_protection-v1beta1
|
157
|
+
is a version-specific client library. For most uses, we recommend installing the
|
158
|
+
main client library google-cloud-phishing_protection instead. See the readme for
|
159
|
+
more details.
|
157
160
|
email: googleapis-packages@google.com
|
158
161
|
executables: []
|
159
162
|
extensions: []
|