google-cloud-binary_authorization 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8bcd184ef654c0d161f87144f832afb8a4dd4edf86ac26afb3b0e50dc19a72d3
-  data.tar.gz: 6370088635b2fcc18cdea2c622eef834e6323459205841c5e5e6d2047f6a4a17
+  metadata.gz: 3fe02626f27846532767a051ef3a5632b2e5588d8f0eee81e1f3bd4b1ece5129
+  data.tar.gz: 8f5031dd6db62e2aa40a398f0c99d89b5d9246d78d30b779ef94bc7142d6f211
 SHA512:
-  metadata.gz: e6b19dd878e9dbfe18f342f6f55af60913360ca64366084140bd1fd19b2ec8ae9bc30faf197dc3906d23a9bbca69264a0ccda58188153a41d846978c19407afa
-  data.tar.gz: bd2d3c8e8a95902415de1de5fab2f3226d8df5fc62e439ffc136f33702e1c25e4c47302d6797596dd317f0649f4ae62d70f7806ec7ec2497541fcf7105d01893
+  metadata.gz: 1cd507bdd290935647a5fbea8d2efb19686d1c25e37c5e643a24e3e6eedd1db9ae182584d89493a22757f63cec0ffc34ab45fd2c1a2dd533a73d8c7a5df6c254
+  data.tar.gz: 53ef1a083e874f220a66cfe0eee62ad2aa1e5d88d69a6d968d45fabb9a8afc20bb78abf5838956603a94749a2a360b4bfc9e90171d4d6a199bf494c46185e762

data/README.md

@@ -6,9 +6,10 @@ Binary Authorization is a service on Google Cloud that provides centralized soft
 
 Actual client classes for the various versions of this API are defined in
 _versioned_ client gems, with names of the form `google-cloud-binary_authorization-v*`.
-The gem `google-cloud-binary_authorization` is a convenience wrapper library that brings the
+The gem `google-cloud-binary_authorization` is the main client library that brings the
 verisoned gems in as dependencies, and provides high-level methods for
-constructing clients.
+constructing clients. More information on versioned clients can be found below
+in the section titled *Which client should I use?*.
 
 View the [Client Library Documentation](https://googleapis.dev/ruby/google-cloud-binary_authorization/latest)
 for this library, google-cloud-binary_authorization, to see the convenience methods for
@@ -69,3 +70,61 @@ in security maintenance, and not end of life. Currently, this means Ruby 2.4
 and later. Older versions of Ruby _may_ still work, but are unsupported and not
 recommended. See https://www.ruby-lang.org/en/downloads/branches/ for details
 about the Ruby support schedule.
+
+## Which client should I use?
+
+Most modern Ruby client libraries for Google APIs come in two flavors: the main
+client library with a name such as `google-cloud-binary_authorization`,
+and lower-level _versioned_ client libraries with names such as
+`google-cloud-binary_authorization-v1beta1`.
+_In most cases, you should install the main client._
+
+### What's the difference between the main client and a versioned client?
+
+A _versioned client_ provides a basic set of data types and client classes for
+a _single version_ of a specific service. (That is, for a service with multiple
+versions, there might be a separate versioned client for each service version.)
+Most versioned clients are written and maintained by a code generator.
+
+The _main client_ is designed to provide you with the _recommended_ client
+interfaces for the service. There will be only one main client for any given
+service, even a service with multiple versions. The main client includes
+factory methods for constructing the client objects we recommend for most
+users. In some cases, those will be classes provided by an underlying versioned
+client; in other cases, they will be handwritten higher-level client objects
+with additional capabilities, convenience methods, or best practices built in.
+Generally, the main client will default to a recommended service version,
+although in some cases you can override this if you need to talk to a specific
+service version.
+
+### Why would I want to use the main client?
+
+We recommend that most users install the main client gem for a service. You can
+identify this gem as the one _without_ a version in its name, e.g.
+`google-cloud-binary_authorization`.
+The main client is recommended because it will embody the best practices for
+accessing the service, and may also provide more convenient interfaces or
+tighter integration into frameworks and third-party libraries. In addition, the
+documentation and samples published by Google will generally demonstrate use of
+the main client.
+
+### Why would I want to use a versioned client?
+
+You can use a versioned client if you are content with a possibly lower-level
+class interface, you explicitly want to avoid features provided by the main
+client, or you want to access a specific service version not be covered by the
+main client. You can identify versioned client gems because the service version
+is part of the name, e.g. `google-cloud-binary_authorization-v1beta1`.
+
+### What about the google-apis-<name> clients?
+
+Client library gems with names that begin with `google-apis-` are based on an
+older code generation technology. They talk to a REST/JSON backend (whereas
+most modern clients talk to a [gRPC](https://grpc.io/) backend) and they may
+not offer the same performance, features, and ease of use provided by more
+modern clients.
+
+The `google-apis-` clients have wide coverage across Google services, so you
+might need to use one if there is no modern client available for the service.
+However, if a modern client is available, we generally recommend it over the
+older `google-apis-` clients.

data/lib/google/cloud/binary_authorization/version.rb

@@ -20,7 +20,7 @@
 module Google
   module Cloud
     module BinaryAuthorization
-      VERSION = "0.1.1"
+      VERSION = "0.1.2"
     end
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-cloud-binary_authorization
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-01-20 00:00:00.000000000 Z
+date: 2021-02-02 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-cloud-binary_authorization-v1beta1