google-cloud-apigee_registry-v1 0.15.0 → 0.17.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 99467223cde1af032df39139d7ea20639fb754e40afa283ede51696da0ed5364
-  data.tar.gz: a95ef6ddeeed1827aaae61179b2d3d1a7dcd3b798da07a446021b3c0e2a69952
+  metadata.gz: cc7c992784566492f54a52820af7710d46e20cd27bde4041e556b74035cd3e4a
+  data.tar.gz: 9c3b34662cfaf2c9318ac5aa3c5f848562a4949746a2bca80ca8bcc42a5fedc3
 SHA512:
-  metadata.gz: 3d6b4cda6dd393cfdd701c55340a54e2ba93d63cb8730f5e1cd9a4c0eaf21f4e859e08ae749878129118db45f8945d7d10792250125b23f1d2bc4bb0a2f1a450
-  data.tar.gz: c341c031f96d8f84de1db8fc2b017b338eefd132b203f3ca8c817bfc722e06a7d297da89bc1013150b33221c03e765028a31ff681a2b88eeb24f3e0e23a7d8f6
+  metadata.gz: e285148421d07634c326a42a787b5877c384bc1837ef97e4d0ac10c903e186e7302ef5fa317c4e4bb2ff356c479d3a24bb1649c69272acfef6951ec8352cd397
+  data.tar.gz: b2a134cd105abc8762a6c09a132db8abb8fe7cf38c4527e745d17462f190615f16754cea8098edf4b0509e39e3502865060bc8a0fb215582ff910e68f2d5e269

data/.yardopts

@@ -1,12 +1,9 @@
 --no-private
---title="Apigee Registry V1 API"
---exclude _pb\.rb$
+--title="Obsolete Gem google-cloud-apigee_registry-v1"
 --markup markdown
 --markup-provider redcarpet
 
 ./lib/**/*.rb
-./proto_docs/**/*.rb
 -
 README.md
 LICENSE.md
-AUTHENTICATION.md

data/LICENSE.md

@@ -1,6 +1,6 @@
                                   Apache License
                             Version 2.0, January 2004
-                         http://www.apache.org/licenses/
+                         https://www.apache.org/licenses/
 
     TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
 
@@ -192,7 +192,7 @@
     you may not use this file except in compliance with the License.
     You may obtain a copy of the License at
 
-       http://www.apache.org/licenses/LICENSE-2.0
+       https://www.apache.org/licenses/LICENSE-2.0
 
     Unless required by applicable law or agreed to in writing, software
     distributed under the License is distributed on an "AS IS" BASIS,

data/README.md

@@ -1,154 +1,4 @@
-# Ruby Client for the Apigee Registry V1 API
+# Tombstone for Ruby gem google-cloud-apigee_registry-v1
 
-API Client library for the Apigee Registry V1 API
-
-The Apigee Registry API allows teams to upload and share machine-readable descriptions of APIs that are in use and in development. These descriptions include API specifications in standard formats like OpenAPI, the Google API Discovery Service Format, and the Protocol Buffers Language. These API specifications can be used by tools like linters, browsers, documentation generators, test runners, proxies, and API client and server generators. The Registry API itself can be seen as a machine-readable enterprise API catalog designed to back online directories, portals, and workflow managers.
-
-https://github.com/googleapis/google-cloud-ruby
-
-This gem is a _versioned_ client. It provides basic client classes for a
-specific version of the Apigee Registry V1 API. Most users should consider using
-the main client gem,
-[google-cloud-apigee_registry](https://rubygems.org/gems/google-cloud-apigee_registry).
-See the section below titled *Which client should I use?* for more information.
-
-## Installation
-
-```
-$ gem install google-cloud-apigee_registry-v1
-```
-
-## Before You Begin
-
-In order to use this library, you first need to go through the following steps:
-
-1. [Select or create a Cloud Platform project.](https://console.cloud.google.com/project)
-1. [Enable billing for your project.](https://cloud.google.com/billing/docs/how-to/modify-project#enable_billing_for_a_project)
-1. [Enable the API.](https://console.cloud.google.com/apis/library/apigeeregistry.googleapis.com)
-1. {file:AUTHENTICATION.md Set up authentication.}
-
-## Quick Start
-
-```ruby
-require "google/cloud/apigee_registry/v1"
-
-client = ::Google::Cloud::ApigeeRegistry::V1::Provisioning::Client.new
-request = ::Google::Cloud::ApigeeRegistry::V1::CreateInstanceRequest.new # (request fields as keyword arguments...)
-response = client.create_instance request
-```
-
-View the [Client Library Documentation](https://cloud.google.com/ruby/docs/reference/google-cloud-apigee_registry-v1/latest)
-for class and method documentation.
-
-See also the [Product Documentation](https://cloud.google.com/apigee/docs/api-hub/get-started-registry-api/)
-for general usage information.
-
-## Debug Logging
-
-This library comes with opt-in Debug Logging that can help you troubleshoot
-your application's integration with the API. When logging is activated, key
-events such as requests and responses, along with data payloads and metadata
-such as headers and client configuration, are logged to the standard error
-stream.
-
-**WARNING:** Client Library Debug Logging includes your data payloads in
-plaintext, which could include sensitive data such as PII for yourself or your
-customers, private keys, or other security data that could be compromising if
-leaked. Always practice good data hygiene with your application logs, and follow
-the principle of least access. Google also recommends that Client Library Debug
-Logging be enabled only temporarily during active debugging, and not used
-permanently in production.
-
-To enable logging, set the environment variable `GOOGLE_SDK_RUBY_LOGGING_GEMS`
-to the value `all`. Alternatively, you can set the value to a comma-delimited
-list of client library gem names. This will select the default logging behavior,
-which writes logs to the standard error stream. On a local workstation, this may
-result in logs appearing on the console. When running on a Google Cloud hosting
-service such as [Google Cloud Run](https://cloud.google.com/run), this generally
-results in logs appearing alongside your application logs in the
-[Google Cloud Logging](https://cloud.google.com/logging/) service.
-
-You can customize logging by modifying the `logger` configuration when
-constructing a client object. For example:
-
-```ruby
-require "google/cloud/apigee_registry/v1"
-require "logger"
-
-client = ::Google::Cloud::ApigeeRegistry::V1::Provisioning::Client.new do |config|
-  config.logger = Logger.new "my-app.log"
-end
-```
-
-## Google Cloud Samples
-
-To browse ready to use code samples check [Google Cloud Samples](https://cloud.google.com/docs/samples).
-
-## Supported Ruby Versions
-
-This library is supported on Ruby 3.0+.
-
-Google provides official support for Ruby versions that are actively supported
-by Ruby Core—that is, Ruby versions that are either in normal maintenance or
-in security maintenance, and not end of life. 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-apigee_registry`,
-and lower-level _versioned_ client libraries with names such as
-`google-cloud-apigee_registry-v1`.
-_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-apigee_registry`.
-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-apigee_registry-v1`.
-
-### 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.
+This gem is obsolete because the related Google backend is turned down.
+For more information, see https://cloud.google.com/terms/deprecation.

data/lib/google/cloud/apigee_registry/v1/version.rb

@@ -21,7 +21,7 @@ module Google
   module Cloud
     module ApigeeRegistry
       module V1
-        VERSION = "0.15.0"
+        VERSION = "0.17.0"
       end
     end
   end

metadata

@@ -1,136 +1,37 @@
 --- !ruby/object:Gem::Specification
 name: google-cloud-apigee_registry-v1
 version: !ruby/object:Gem::Version
-  version: 0.15.0
+  version: 0.17.0
 platform: ruby
 authors:
 - Google LLC
 bindir: bin
 cert_chain: []
 date: 1980-01-02 00:00:00.000000000 Z
-dependencies:
-- !ruby/object:Gem::Dependency
-  name: gapic-common
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.2'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.2'
-- !ruby/object:Gem::Dependency
-  name: google-cloud-errors
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.0'
-- !ruby/object:Gem::Dependency
-  name: google-cloud-location
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.0'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.0'
-- !ruby/object:Gem::Dependency
-  name: google-iam-v1
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.3'
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '1.3'
-description: The Apigee Registry API allows teams to upload and share machine-readable
-  descriptions of APIs that are in use and in development. These descriptions include
-  API specifications in standard formats like OpenAPI, the Google API Discovery Service
-  Format, and the Protocol Buffers Language. These API specifications can be used
-  by tools like linters, browsers, documentation generators, test runners, proxies,
-  and API client and server generators. The Registry API itself can be seen as a machine-readable
-  enterprise API catalog designed to back online directories, portals, and workflow
-  managers. Note that google-cloud-apigee_registry-v1 is a version-specific client
-  library. For most uses, we recommend installing the main client library google-cloud-apigee_registry
-  instead. See the readme for more details.
+dependencies: []
+description: This gem is obsolete because the related Google backend is turned down.
+  For more information, see https://cloud.google.com/terms/deprecation.
 email: googleapis-packages@google.com
 executables: []
 extensions: []
 extra_rdoc_files: []
 files:
 - ".yardopts"
-- AUTHENTICATION.md
 - LICENSE.md
 - README.md
-- lib/google-cloud-apigee_registry-v1.rb
-- lib/google/cloud/apigee_registry/v1.rb
-- lib/google/cloud/apigee_registry/v1/bindings_override.rb
-- lib/google/cloud/apigee_registry/v1/provisioning.rb
-- lib/google/cloud/apigee_registry/v1/provisioning/client.rb
-- lib/google/cloud/apigee_registry/v1/provisioning/credentials.rb
-- lib/google/cloud/apigee_registry/v1/provisioning/operations.rb
-- lib/google/cloud/apigee_registry/v1/provisioning/paths.rb
-- lib/google/cloud/apigee_registry/v1/provisioning/rest.rb
-- lib/google/cloud/apigee_registry/v1/provisioning/rest/client.rb
-- lib/google/cloud/apigee_registry/v1/provisioning/rest/operations.rb
-- lib/google/cloud/apigee_registry/v1/provisioning/rest/service_stub.rb
-- lib/google/cloud/apigee_registry/v1/registry.rb
-- lib/google/cloud/apigee_registry/v1/registry/client.rb
-- lib/google/cloud/apigee_registry/v1/registry/credentials.rb
-- lib/google/cloud/apigee_registry/v1/registry/paths.rb
-- lib/google/cloud/apigee_registry/v1/registry/rest.rb
-- lib/google/cloud/apigee_registry/v1/registry/rest/client.rb
-- lib/google/cloud/apigee_registry/v1/registry/rest/service_stub.rb
-- lib/google/cloud/apigee_registry/v1/rest.rb
 - lib/google/cloud/apigee_registry/v1/version.rb
-- lib/google/cloud/apigeeregistry/v1/provisioning_service_pb.rb
-- lib/google/cloud/apigeeregistry/v1/provisioning_service_services_pb.rb
-- lib/google/cloud/apigeeregistry/v1/registry_models_pb.rb
-- lib/google/cloud/apigeeregistry/v1/registry_service_pb.rb
-- lib/google/cloud/apigeeregistry/v1/registry_service_services_pb.rb
-- proto_docs/README.md
-- proto_docs/google/api/client.rb
-- proto_docs/google/api/field_behavior.rb
-- proto_docs/google/api/httpbody.rb
-- proto_docs/google/api/launch_stage.rb
-- proto_docs/google/api/resource.rb
-- proto_docs/google/cloud/apigeeregistry/v1/provisioning_service.rb
-- proto_docs/google/cloud/apigeeregistry/v1/registry_models.rb
-- proto_docs/google/cloud/apigeeregistry/v1/registry_service.rb
-- proto_docs/google/longrunning/operations.rb
-- proto_docs/google/protobuf/any.rb
-- proto_docs/google/protobuf/duration.rb
-- proto_docs/google/protobuf/empty.rb
-- proto_docs/google/protobuf/field_mask.rb
-- proto_docs/google/protobuf/timestamp.rb
-- proto_docs/google/rpc/status.rb
-- proto_docs/google/type/expr.rb
 homepage: https://github.com/googleapis/google-cloud-ruby
 licenses:
 - Apache-2.0
 metadata: {}
+post_install_message: |2+
+
+  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+  The google-cloud-apigee_registry-v1 gem is OBSOLETE.
+  For more information, see:
+  https://cloud.google.com/terms/deprecation
+  !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
 rdoc_options: []
 require_paths:
 - lib
@@ -138,7 +39,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '3.2'
+      version: '3.0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
@@ -147,5 +48,6 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 rubygems_version: 3.6.9
 specification_version: 4
-summary: API Client library for the Apigee Registry V1 API
+summary: This gem is obsolete because the related backend is turned down.
 test_files: []
+...

data/AUTHENTICATION.md

@@ -1,122 +0,0 @@
-# Authentication
-
-The recommended way to authenticate to the google-cloud-apigee_registry-v1 library is to use
-[Application Default Credentials (ADC)](https://cloud.google.com/docs/authentication/application-default-credentials).
-To review all of your authentication options, see [Credentials lookup](#credential-lookup).
-
-## Quickstart
-
-The following example shows how to set up authentication for a local development
-environment with your user credentials. 
-
-**NOTE:** This method is _not_ recommended for running in production. User credentials
-should be used only during development.
-
-1. [Download and install the Google Cloud CLI](https://cloud.google.com/sdk).
-2. Set up a local ADC file with your user credentials:
-
-```sh
-gcloud auth application-default login
-```
-
-3. Write code as if already authenticated.
-
-For more information about setting up authentication for a local development environment, see
-[Set up Application Default Credentials](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-dev).
-
-## Credential Lookup
-
-The google-cloud-apigee_registry-v1 library provides several mechanisms to configure your system.
-Generally, using Application Default Credentials to facilitate automatic 
-credentials discovery is the easist method. But if you need to explicitly specify
-credentials, there are several methods available to you.
-
-Credentials are accepted in the following ways, in the following order or precedence:
-
-1. Credentials specified in method arguments
-2. Credentials specified in configuration
-3. Credentials pointed to or included in environment variables
-4. Credentials found in local ADC file
-5. Credentials returned by the metadata server for the attached service account (GCP)
-
-### Configuration
-
-You can configure a path to a JSON credentials file, either for an individual client object or
-globally, for all client objects. The JSON file can contain credentials created for
-[workload identity federation](https://cloud.google.com/iam/docs/workload-identity-federation),
-[workforce identity federation](https://cloud.google.com/iam/docs/workforce-identity-federation), or a
-[service account key](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-key).
-
-Note: Service account keys are a security risk if not managed correctly. You should
-[choose a more secure alternative to service account keys](https://cloud.google.com/docs/authentication#auth-decision-tree)
-whenever possible.
-
-To configure a credentials file for an individual client initialization:
-
-```ruby
-require "google/cloud/apigee_registry/v1"
-
-client = ::Google::Cloud::ApigeeRegistry::V1::Provisioning::Client.new do |config|
-  config.credentials = "path/to/credentialfile.json"
-end
-```
-
-To configure a credentials file globally for all clients:
-
-```ruby
-require "google/cloud/apigee_registry/v1"
-
-::Google::Cloud::ApigeeRegistry::V1::Provisioning::Client.configure do |config|
-  config.credentials = "path/to/credentialfile.json"
-end
-
-client = ::Google::Cloud::ApigeeRegistry::V1::Provisioning::Client.new
-```
-
-### Environment Variables
-
-You can also use an environment variable to provide a JSON credentials file.
-The environment variable can contain a path to the credentials file or, for
-environments such as Docker containers where writing files is not encouraged,
-you can include the credentials file itself.
-
-The JSON file can contain credentials created for
-[workload identity federation](https://cloud.google.com/iam/docs/workload-identity-federation),
-[workforce identity federation](https://cloud.google.com/iam/docs/workforce-identity-federation), or a
-[service account key](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-key).
-
-Note: Service account keys are a security risk if not managed correctly. You should
-[choose a more secure alternative to service account keys](https://cloud.google.com/docs/authentication#auth-decision-tree)
-whenever possible.
-
-The environment variables that google-cloud-apigee_registry-v1
-checks for credentials are:
-
-* `GOOGLE_CLOUD_CREDENTIALS` - Path to JSON file, or JSON contents
-* `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file
-
-```ruby
-require "google/cloud/apigee_registry/v1"
-
-ENV["GOOGLE_APPLICATION_CREDENTIALS"] = "path/to/credentialfile.json"
-
-client = ::Google::Cloud::ApigeeRegistry::V1::Provisioning::Client.new
-```
-
-### Local ADC file
-
-You can set up a local ADC file with your user credentials for authentication during
-development. If credentials are not provided in code or in environment variables,
-then the local ADC credentials are discovered.
-
-Follow the steps in [Quickstart](#quickstart) to set up a local ADC file.
-
-### Google Cloud Platform environments
-
-When running on Google Cloud Platform (GCP), including Google Compute Engine
-(GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud
-Functions (GCF) and Cloud Run, credentials are retrieved from the attached
-service account automatically. Code should be written as if already authenticated.
-
-For more information, see
-[Set up ADC for Google Cloud services](https://cloud.google.com/docs/authentication/provide-credentials-adc#attached-sa).