grafeas-v1 0.1.3 → 0.1.4
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +64 -0
- data/lib/grafeas/v1/version.rb +1 -1
- data/proto_docs/google/api/field_behavior.rb +6 -0
- data/proto_docs/google/protobuf/any.rb +5 -2
- data/proto_docs/google/protobuf/timestamp.rb +10 -1
- metadata +5 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 4c98ba2b171f4df5ab6ba2a9549a4fe05a8cdd3b6ecaa81d1430056d4a517927
|
4
|
+
data.tar.gz: 19c3c16cc8128c9fd3fdea2a752950068d08809a60374d8e5fd882bb5c7e467d
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 67c6257cdf4b7863a94ad250ad27daa9a49c1337fd6721655e4f9b2ff5931e6a650bd6355bc9727bda945548e33241794ad99af42ab134ac5eb753478c89f9bd
|
7
|
+
data.tar.gz: b34bd16645ba75af30ed522283873675fd794e0a0c5375e198dbaba0afe72419fd0d3ff985d643a93a4b8686a08cf22464cc6874156ba56da1cc2bdad13bad8e
|
data/README.md
CHANGED
@@ -6,6 +6,12 @@ The Grafeas API stores, and enables querying and retrieval of, critical metadata
|
|
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 Grafeas V1 API. Most users should consider using
|
11
|
+
the main client gem,
|
12
|
+
[grafeas](https://rubygems.org/gems/grafeas).
|
13
|
+
See the section below titled *Which client should I use?* for more information.
|
14
|
+
|
9
15
|
## Installation
|
10
16
|
|
11
17
|
```
|
@@ -61,3 +67,61 @@ in security maintenance, and not end of life. Currently, this means Ruby 2.4
|
|
61
67
|
and later. Older versions of Ruby _may_ still work, but are unsupported and not
|
62
68
|
recommended. See https://www.ruby-lang.org/en/downloads/branches/ for details
|
63
69
|
about the Ruby support schedule.
|
70
|
+
|
71
|
+
## Which client should I use?
|
72
|
+
|
73
|
+
Most modern Ruby client libraries for Google APIs come in two flavors: the main
|
74
|
+
client library with a name such as `grafeas`,
|
75
|
+
and lower-level _versioned_ client libraries with names such as
|
76
|
+
`grafeas-v1`.
|
77
|
+
_In most cases, you should install the main client._
|
78
|
+
|
79
|
+
### What's the difference between the main client and a versioned client?
|
80
|
+
|
81
|
+
A _versioned client_ provides a basic set of data types and client classes for
|
82
|
+
a _single version_ of a specific service. (That is, for a service with multiple
|
83
|
+
versions, there might be a separate versioned client for each service version.)
|
84
|
+
Most versioned clients are written and maintained by a code generator.
|
85
|
+
|
86
|
+
The _main client_ is designed to provide you with the _recommended_ client
|
87
|
+
interfaces for the service. There will be only one main client for any given
|
88
|
+
service, even a service with multiple versions. The main client includes
|
89
|
+
factory methods for constructing the client objects we recommend for most
|
90
|
+
users. In some cases, those will be classes provided by an underlying versioned
|
91
|
+
client; in other cases, they will be handwritten higher-level client objects
|
92
|
+
with additional capabilities, convenience methods, or best practices built in.
|
93
|
+
Generally, the main client will default to a recommended service version,
|
94
|
+
although in some cases you can override this if you need to talk to a specific
|
95
|
+
service version.
|
96
|
+
|
97
|
+
### Why would I want to use the main client?
|
98
|
+
|
99
|
+
We recommend that most users install the main client gem for a service. You can
|
100
|
+
identify this gem as the one _without_ a version in its name, e.g.
|
101
|
+
`grafeas`.
|
102
|
+
The main client is recommended because it will embody the best practices for
|
103
|
+
accessing the service, and may also provide more convenient interfaces or
|
104
|
+
tighter integration into frameworks and third-party libraries. In addition, the
|
105
|
+
documentation and samples published by Google will generally demonstrate use of
|
106
|
+
the main client.
|
107
|
+
|
108
|
+
### Why would I want to use a versioned client?
|
109
|
+
|
110
|
+
You can use a versioned client if you are content with a possibly lower-level
|
111
|
+
class interface, you explicitly want to avoid features provided by the main
|
112
|
+
client, or you want to access a specific service version not be covered by the
|
113
|
+
main client. You can identify versioned client gems because the service version
|
114
|
+
is part of the name, e.g. `grafeas-v1`.
|
115
|
+
|
116
|
+
### What about the google-apis-<name> clients?
|
117
|
+
|
118
|
+
Client library gems with names that begin with `google-apis-` are based on an
|
119
|
+
older code generation technology. They talk to a REST/JSON backend (whereas
|
120
|
+
most modern clients talk to a [gRPC](https://grpc.io/) backend) and they may
|
121
|
+
not offer the same performance, features, and ease of use provided by more
|
122
|
+
modern clients.
|
123
|
+
|
124
|
+
The `google-apis-` clients have wide coverage across Google services, so you
|
125
|
+
might need to use one if there is no modern client available for the service.
|
126
|
+
However, if a modern client is available, we generally recommend it over the
|
127
|
+
older `google-apis-` clients.
|
data/lib/grafeas/v1/version.rb
CHANGED
@@ -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
|
@@ -57,10 +57,13 @@ module Google
|
|
57
57
|
# Example 4: Pack and unpack a message in Go
|
58
58
|
#
|
59
59
|
# foo := &pb.Foo{...}
|
60
|
-
# any, err :=
|
60
|
+
# any, err := anypb.New(foo)
|
61
|
+
# if err != nil {
|
62
|
+
# ...
|
63
|
+
# }
|
61
64
|
# ...
|
62
65
|
# foo := &pb.Foo{}
|
63
|
-
# if err :=
|
66
|
+
# if err := any.UnmarshalTo(foo); err != nil {
|
64
67
|
# ...
|
65
68
|
# }
|
66
69
|
#
|
@@ -70,7 +70,16 @@ module Google
|
|
70
70
|
# .setNanos((int) ((millis % 1000) * 1000000)).build();
|
71
71
|
#
|
72
72
|
#
|
73
|
-
# Example 5: Compute Timestamp from
|
73
|
+
# Example 5: Compute Timestamp from Java `Instant.now()`.
|
74
|
+
#
|
75
|
+
# Instant now = Instant.now();
|
76
|
+
#
|
77
|
+
# Timestamp timestamp =
|
78
|
+
# Timestamp.newBuilder().setSeconds(now.getEpochSecond())
|
79
|
+
# .setNanos(now.getNano()).build();
|
80
|
+
#
|
81
|
+
#
|
82
|
+
# Example 6: Compute Timestamp from current time in Python.
|
74
83
|
#
|
75
84
|
# timestamp = Timestamp()
|
76
85
|
# timestamp.GetCurrentTime()
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: grafeas-v1
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.1.
|
4
|
+
version: 0.1.4
|
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
|
@@ -151,7 +151,9 @@ dependencies:
|
|
151
151
|
- !ruby/object:Gem::Version
|
152
152
|
version: '0.9'
|
153
153
|
description: The Grafeas API stores, and enables querying and retrieval of, critical
|
154
|
-
metadata about all of your software artifacts.
|
154
|
+
metadata about all of your software artifacts. Note that grafeas-v1 is a version-specific
|
155
|
+
client library. For most uses, we recommend installing the main client library grafeas
|
156
|
+
instead. See the readme for more details.
|
155
157
|
email: googleapis-packages@google.com
|
156
158
|
executables: []
|
157
159
|
extensions: []
|