google-cloud-apigee_registry 1.4.0 → 2.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/.yardopts +1 -3
- data/LICENSE.md +2 -2
- data/README.md +3 -141
- data/lib/google/cloud/apigee_registry/version.rb +1 -1
- metadata +15 -49
- data/AUTHENTICATION.md +0 -122
- data/lib/google/cloud/apigee_registry.rb +0 -227
- data/lib/google-cloud-apigee_registry.rb +0 -19
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 6dab123c04a0ef70eaa7c9c6c7e134e4b108faecec74966b2e009c3f19c739c6
|
|
4
|
+
data.tar.gz: 1c74a2d49c6bbda3cc8159b8a1150ec0306122f131f6ad8460c1a8208b15ee91
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: f703d14ba98567b6f5c2c917d495991a0c99fd73699af76996304c0d0c503f07214bc9194ff15ecb3d9eaddfc1958b1dcf699949318207a769b925b906c7d4c6
|
|
7
|
+
data.tar.gz: 032b235a3f267d2217f57a9481a3deb784112937cb0815eaf822aba7f792a554edbd3b89bd3a7a5a0fa2bab80ceb3abf7508aaa9cf9af5d3d9b2c28587822c9c
|
data/.yardopts
CHANGED
data/LICENSE.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Apache License
|
|
2
2
|
Version 2.0, January 2004
|
|
3
|
-
|
|
3
|
+
https://www.apache.org/licenses/
|
|
4
4
|
|
|
5
5
|
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
6
|
|
|
@@ -192,7 +192,7 @@
|
|
|
192
192
|
you may not use this file except in compliance with the License.
|
|
193
193
|
You may obtain a copy of the License at
|
|
194
194
|
|
|
195
|
-
|
|
195
|
+
https://www.apache.org/licenses/LICENSE-2.0
|
|
196
196
|
|
|
197
197
|
Unless required by applicable law or agreed to in writing, software
|
|
198
198
|
distributed under the License is distributed on an "AS IS" BASIS,
|
data/README.md
CHANGED
|
@@ -1,142 +1,4 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Tombstone for Ruby gem google-cloud-apigee_registry
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
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.
|
|
6
|
-
|
|
7
|
-
Actual client classes for the various versions of this API are defined in
|
|
8
|
-
_versioned_ client gems, with names of the form `google-cloud-apigee_registry-v*`.
|
|
9
|
-
The gem `google-cloud-apigee_registry` is the main client library that brings the
|
|
10
|
-
versioned gems in as dependencies, and provides high-level methods for
|
|
11
|
-
constructing clients. More information on versioned clients can be found below
|
|
12
|
-
in the section titled *Which client should I use?*.
|
|
13
|
-
|
|
14
|
-
View the [Client Library Documentation](https://cloud.google.com/ruby/docs/reference/google-cloud-apigee_registry/latest)
|
|
15
|
-
for this library, google-cloud-apigee_registry, to see the convenience methods for
|
|
16
|
-
constructing client objects. Reference documentation for the client objects
|
|
17
|
-
themselves can be found in the client library documentation for the versioned
|
|
18
|
-
client gems:
|
|
19
|
-
[google-cloud-apigee_registry-v1](https://cloud.google.com/ruby/docs/reference/google-cloud-apigee_registry-v1/latest).
|
|
20
|
-
|
|
21
|
-
See also the [Product Documentation](https://cloud.google.com/apigee/docs/api-hub/get-started-registry-api/)
|
|
22
|
-
for more usage information.
|
|
23
|
-
|
|
24
|
-
## Quick Start
|
|
25
|
-
|
|
26
|
-
```
|
|
27
|
-
$ gem install google-cloud-apigee_registry
|
|
28
|
-
```
|
|
29
|
-
|
|
30
|
-
In order to use this library, you first need to go through the following steps:
|
|
31
|
-
|
|
32
|
-
1. [Select or create a Cloud Platform project.](https://console.cloud.google.com/project)
|
|
33
|
-
1. [Enable billing for your project.](https://cloud.google.com/billing/docs/how-to/modify-project#enable_billing_for_a_project)
|
|
34
|
-
1. [Enable the API.](https://console.cloud.google.com/apis/library/apigeeregistry.googleapis.com)
|
|
35
|
-
1. {file:AUTHENTICATION.md Set up authentication.}
|
|
36
|
-
|
|
37
|
-
```ruby
|
|
38
|
-
require "google/cloud/apigee_registry"
|
|
39
|
-
|
|
40
|
-
client = Google::Cloud::ApigeeRegistry.provisioning
|
|
41
|
-
request = ::Google::Cloud::ApigeeRegistry::V1::CreateInstanceRequest.new # (request fields as keyword arguments...)
|
|
42
|
-
response = client.create_instance request
|
|
43
|
-
```
|
|
44
|
-
|
|
45
|
-
## Debug Logging
|
|
46
|
-
|
|
47
|
-
This library comes with opt-in Debug Logging that can help you troubleshoot
|
|
48
|
-
your application's integration with the API. When logging is activated, key
|
|
49
|
-
events such as requests and responses, along with data payloads and metadata
|
|
50
|
-
such as headers and client configuration, are logged to the standard error
|
|
51
|
-
stream.
|
|
52
|
-
|
|
53
|
-
**WARNING:** Client Library Debug Logging includes your data payloads in
|
|
54
|
-
plaintext, which could include sensitive data such as PII for yourself or your
|
|
55
|
-
customers, private keys, or other security data that could be compromising if
|
|
56
|
-
leaked. Always practice good data hygiene with your application logs, and follow
|
|
57
|
-
the principle of least access. Google also recommends that Client Library Debug
|
|
58
|
-
Logging be enabled only temporarily during active debugging, and not used
|
|
59
|
-
permanently in production.
|
|
60
|
-
|
|
61
|
-
To enable logging, set the environment variable `GOOGLE_SDK_RUBY_LOGGING_GEMS`
|
|
62
|
-
to the value `all`. Alternatively, you can set the value to a comma-delimited
|
|
63
|
-
list of client library gem names. This will select the default logging behavior,
|
|
64
|
-
which writes logs to the standard error stream. On a local workstation, this may
|
|
65
|
-
result in logs appearing on the console. When running on a Google Cloud hosting
|
|
66
|
-
service such as [Google Cloud Run](https://cloud.google.com/run), this generally
|
|
67
|
-
results in logs appearing alongside your application logs in the
|
|
68
|
-
[Google Cloud Logging](https://cloud.google.com/logging/) service.
|
|
69
|
-
|
|
70
|
-
Debug logging also requires that the versioned clients for this service be
|
|
71
|
-
sufficiently recent, released after about Dec 10, 2024. If logging is not
|
|
72
|
-
working, try updating the versioned clients in your bundle or installed gems:
|
|
73
|
-
[google-cloud-apigee_registry-v1](https://cloud.google.com/ruby/docs/reference/google-cloud-apigee_registry-v1/latest).
|
|
74
|
-
|
|
75
|
-
## Supported Ruby Versions
|
|
76
|
-
|
|
77
|
-
This library is supported on Ruby 3.0+.
|
|
78
|
-
|
|
79
|
-
Google provides official support for Ruby versions that are actively supported
|
|
80
|
-
by Ruby Core—that is, Ruby versions that are either in normal maintenance or
|
|
81
|
-
in security maintenance, and not end of life. Older versions of Ruby _may_
|
|
82
|
-
still work, but are unsupported and not recommended. See
|
|
83
|
-
https://www.ruby-lang.org/en/downloads/branches/ for details about the Ruby
|
|
84
|
-
support schedule.
|
|
85
|
-
|
|
86
|
-
## Which client should I use?
|
|
87
|
-
|
|
88
|
-
Most modern Ruby client libraries for Google APIs come in two flavors: the main
|
|
89
|
-
client library with a name such as `google-cloud-apigee_registry`,
|
|
90
|
-
and lower-level _versioned_ client libraries with names such as
|
|
91
|
-
`google-cloud-apigee_registry-v1`.
|
|
92
|
-
_In most cases, you should install the main client._
|
|
93
|
-
|
|
94
|
-
### What's the difference between the main client and a versioned client?
|
|
95
|
-
|
|
96
|
-
A _versioned client_ provides a basic set of data types and client classes for
|
|
97
|
-
a _single version_ of a specific service. (That is, for a service with multiple
|
|
98
|
-
versions, there might be a separate versioned client for each service version.)
|
|
99
|
-
Most versioned clients are written and maintained by a code generator.
|
|
100
|
-
|
|
101
|
-
The _main client_ is designed to provide you with the _recommended_ client
|
|
102
|
-
interfaces for the service. There will be only one main client for any given
|
|
103
|
-
service, even a service with multiple versions. The main client includes
|
|
104
|
-
factory methods for constructing the client objects we recommend for most
|
|
105
|
-
users. In some cases, those will be classes provided by an underlying versioned
|
|
106
|
-
client; in other cases, they will be handwritten higher-level client objects
|
|
107
|
-
with additional capabilities, convenience methods, or best practices built in.
|
|
108
|
-
Generally, the main client will default to a recommended service version,
|
|
109
|
-
although in some cases you can override this if you need to talk to a specific
|
|
110
|
-
service version.
|
|
111
|
-
|
|
112
|
-
### Why would I want to use the main client?
|
|
113
|
-
|
|
114
|
-
We recommend that most users install the main client gem for a service. You can
|
|
115
|
-
identify this gem as the one _without_ a version in its name, e.g.
|
|
116
|
-
`google-cloud-apigee_registry`.
|
|
117
|
-
The main client is recommended because it will embody the best practices for
|
|
118
|
-
accessing the service, and may also provide more convenient interfaces or
|
|
119
|
-
tighter integration into frameworks and third-party libraries. In addition, the
|
|
120
|
-
documentation and samples published by Google will generally demonstrate use of
|
|
121
|
-
the main client.
|
|
122
|
-
|
|
123
|
-
### Why would I want to use a versioned client?
|
|
124
|
-
|
|
125
|
-
You can use a versioned client if you are content with a possibly lower-level
|
|
126
|
-
class interface, you explicitly want to avoid features provided by the main
|
|
127
|
-
client, or you want to access a specific service version not be covered by the
|
|
128
|
-
main client. You can identify versioned client gems because the service version
|
|
129
|
-
is part of the name, e.g. `google-cloud-apigee_registry-v1`.
|
|
130
|
-
|
|
131
|
-
### What about the google-apis-<name> clients?
|
|
132
|
-
|
|
133
|
-
Client library gems with names that begin with `google-apis-` are based on an
|
|
134
|
-
older code generation technology. They talk to a REST/JSON backend (whereas
|
|
135
|
-
most modern clients talk to a [gRPC](https://grpc.io/) backend) and they may
|
|
136
|
-
not offer the same performance, features, and ease of use provided by more
|
|
137
|
-
modern clients.
|
|
138
|
-
|
|
139
|
-
The `google-apis-` clients have wide coverage across Google services, so you
|
|
140
|
-
might need to use one if there is no modern client available for the service.
|
|
141
|
-
However, if a modern client is available, we generally recommend it over the
|
|
142
|
-
older `google-apis-` clients.
|
|
3
|
+
This gem is obsolete because the related Google backend is turned down.
|
|
4
|
+
For more information, see https://cloud.google.com/terms/deprecation.
|
metadata
CHANGED
|
@@ -1,72 +1,37 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: google-cloud-apigee_registry
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version:
|
|
4
|
+
version: 2.0.0
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Google LLC
|
|
8
8
|
bindir: bin
|
|
9
9
|
cert_chain: []
|
|
10
10
|
date: 1980-01-02 00:00:00.000000000 Z
|
|
11
|
-
dependencies:
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
requirement: !ruby/object:Gem::Requirement
|
|
15
|
-
requirements:
|
|
16
|
-
- - ">="
|
|
17
|
-
- !ruby/object:Gem::Version
|
|
18
|
-
version: '0.7'
|
|
19
|
-
- - "<"
|
|
20
|
-
- !ruby/object:Gem::Version
|
|
21
|
-
version: 2.a
|
|
22
|
-
type: :runtime
|
|
23
|
-
prerelease: false
|
|
24
|
-
version_requirements: !ruby/object:Gem::Requirement
|
|
25
|
-
requirements:
|
|
26
|
-
- - ">="
|
|
27
|
-
- !ruby/object:Gem::Version
|
|
28
|
-
version: '0.7'
|
|
29
|
-
- - "<"
|
|
30
|
-
- !ruby/object:Gem::Version
|
|
31
|
-
version: 2.a
|
|
32
|
-
- !ruby/object:Gem::Dependency
|
|
33
|
-
name: google-cloud-core
|
|
34
|
-
requirement: !ruby/object:Gem::Requirement
|
|
35
|
-
requirements:
|
|
36
|
-
- - "~>"
|
|
37
|
-
- !ruby/object:Gem::Version
|
|
38
|
-
version: '1.6'
|
|
39
|
-
type: :runtime
|
|
40
|
-
prerelease: false
|
|
41
|
-
version_requirements: !ruby/object:Gem::Requirement
|
|
42
|
-
requirements:
|
|
43
|
-
- - "~>"
|
|
44
|
-
- !ruby/object:Gem::Version
|
|
45
|
-
version: '1.6'
|
|
46
|
-
description: The Apigee Registry API allows teams to upload and share machine-readable
|
|
47
|
-
descriptions of APIs that are in use and in development. These descriptions include
|
|
48
|
-
API specifications in standard formats like OpenAPI, the Google API Discovery Service
|
|
49
|
-
Format, and the Protocol Buffers Language. These API specifications can be used
|
|
50
|
-
by tools like linters, browsers, documentation generators, test runners, proxies,
|
|
51
|
-
and API client and server generators. The Registry API itself can be seen as a machine-readable
|
|
52
|
-
enterprise API catalog designed to back online directories, portals, and workflow
|
|
53
|
-
managers.
|
|
11
|
+
dependencies: []
|
|
12
|
+
description: This gem is obsolete because the related Google backend is turned down.
|
|
13
|
+
For more information, see https://cloud.google.com/terms/deprecation.
|
|
54
14
|
email: googleapis-packages@google.com
|
|
55
15
|
executables: []
|
|
56
16
|
extensions: []
|
|
57
17
|
extra_rdoc_files: []
|
|
58
18
|
files:
|
|
59
19
|
- ".yardopts"
|
|
60
|
-
- AUTHENTICATION.md
|
|
61
20
|
- LICENSE.md
|
|
62
21
|
- README.md
|
|
63
|
-
- lib/google-cloud-apigee_registry.rb
|
|
64
|
-
- lib/google/cloud/apigee_registry.rb
|
|
65
22
|
- lib/google/cloud/apigee_registry/version.rb
|
|
66
23
|
homepage: https://github.com/googleapis/google-cloud-ruby
|
|
67
24
|
licenses:
|
|
68
25
|
- Apache-2.0
|
|
69
26
|
metadata: {}
|
|
27
|
+
post_install_message: |2+
|
|
28
|
+
|
|
29
|
+
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
30
|
+
The google-cloud-apigee_registry gem is OBSOLETE.
|
|
31
|
+
For more information, see:
|
|
32
|
+
https://cloud.google.com/terms/deprecation
|
|
33
|
+
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|
|
34
|
+
|
|
70
35
|
rdoc_options: []
|
|
71
36
|
require_paths:
|
|
72
37
|
- lib
|
|
@@ -74,7 +39,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
|
74
39
|
requirements:
|
|
75
40
|
- - ">="
|
|
76
41
|
- !ruby/object:Gem::Version
|
|
77
|
-
version: '3.
|
|
42
|
+
version: '3.0'
|
|
78
43
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
|
79
44
|
requirements:
|
|
80
45
|
- - ">="
|
|
@@ -83,5 +48,6 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
83
48
|
requirements: []
|
|
84
49
|
rubygems_version: 3.6.9
|
|
85
50
|
specification_version: 4
|
|
86
|
-
summary:
|
|
51
|
+
summary: This gem is obsolete because the related backend is turned down.
|
|
87
52
|
test_files: []
|
|
53
|
+
...
|
data/AUTHENTICATION.md
DELETED
|
@@ -1,122 +0,0 @@
|
|
|
1
|
-
# Authentication
|
|
2
|
-
|
|
3
|
-
The recommended way to authenticate to the google-cloud-apigee_registry library is to use
|
|
4
|
-
[Application Default Credentials (ADC)](https://cloud.google.com/docs/authentication/application-default-credentials).
|
|
5
|
-
To review all of your authentication options, see [Credentials lookup](#credential-lookup).
|
|
6
|
-
|
|
7
|
-
## Quickstart
|
|
8
|
-
|
|
9
|
-
The following example shows how to set up authentication for a local development
|
|
10
|
-
environment with your user credentials.
|
|
11
|
-
|
|
12
|
-
**NOTE:** This method is _not_ recommended for running in production. User credentials
|
|
13
|
-
should be used only during development.
|
|
14
|
-
|
|
15
|
-
1. [Download and install the Google Cloud CLI](https://cloud.google.com/sdk).
|
|
16
|
-
2. Set up a local ADC file with your user credentials:
|
|
17
|
-
|
|
18
|
-
```sh
|
|
19
|
-
gcloud auth application-default login
|
|
20
|
-
```
|
|
21
|
-
|
|
22
|
-
3. Write code as if already authenticated.
|
|
23
|
-
|
|
24
|
-
For more information about setting up authentication for a local development environment, see
|
|
25
|
-
[Set up Application Default Credentials](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-dev).
|
|
26
|
-
|
|
27
|
-
## Credential Lookup
|
|
28
|
-
|
|
29
|
-
The google-cloud-apigee_registry library provides several mechanisms to configure your system.
|
|
30
|
-
Generally, using Application Default Credentials to facilitate automatic
|
|
31
|
-
credentials discovery is the easist method. But if you need to explicitly specify
|
|
32
|
-
credentials, there are several methods available to you.
|
|
33
|
-
|
|
34
|
-
Credentials are accepted in the following ways, in the following order or precedence:
|
|
35
|
-
|
|
36
|
-
1. Credentials specified in method arguments
|
|
37
|
-
2. Credentials specified in configuration
|
|
38
|
-
3. Credentials pointed to or included in environment variables
|
|
39
|
-
4. Credentials found in local ADC file
|
|
40
|
-
5. Credentials returned by the metadata server for the attached service account (GCP)
|
|
41
|
-
|
|
42
|
-
### Configuration
|
|
43
|
-
|
|
44
|
-
You can configure a path to a JSON credentials file, either for an individual client object or
|
|
45
|
-
globally, for all client objects. The JSON file can contain credentials created for
|
|
46
|
-
[workload identity federation](https://cloud.google.com/iam/docs/workload-identity-federation),
|
|
47
|
-
[workforce identity federation](https://cloud.google.com/iam/docs/workforce-identity-federation), or a
|
|
48
|
-
[service account key](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-key).
|
|
49
|
-
|
|
50
|
-
Note: Service account keys are a security risk if not managed correctly. You should
|
|
51
|
-
[choose a more secure alternative to service account keys](https://cloud.google.com/docs/authentication#auth-decision-tree)
|
|
52
|
-
whenever possible.
|
|
53
|
-
|
|
54
|
-
To configure a credentials file for an individual client initialization:
|
|
55
|
-
|
|
56
|
-
```ruby
|
|
57
|
-
require "google/cloud/apigee_registry"
|
|
58
|
-
|
|
59
|
-
client = Google::Cloud::ApigeeRegistry.provisioning do |config|
|
|
60
|
-
config.credentials = "path/to/credentialfile.json"
|
|
61
|
-
end
|
|
62
|
-
```
|
|
63
|
-
|
|
64
|
-
To configure a credentials file globally for all clients:
|
|
65
|
-
|
|
66
|
-
```ruby
|
|
67
|
-
require "google/cloud/apigee_registry"
|
|
68
|
-
|
|
69
|
-
Google::Cloud::ApigeeRegistry.configure do |config|
|
|
70
|
-
config.credentials = "path/to/credentialfile.json"
|
|
71
|
-
end
|
|
72
|
-
|
|
73
|
-
client = Google::Cloud::ApigeeRegistry.provisioning
|
|
74
|
-
```
|
|
75
|
-
|
|
76
|
-
### Environment Variables
|
|
77
|
-
|
|
78
|
-
You can also use an environment variable to provide a JSON credentials file.
|
|
79
|
-
The environment variable can contain a path to the credentials file or, for
|
|
80
|
-
environments such as Docker containers where writing files is not encouraged,
|
|
81
|
-
you can include the credentials file itself.
|
|
82
|
-
|
|
83
|
-
The JSON file can contain credentials created for
|
|
84
|
-
[workload identity federation](https://cloud.google.com/iam/docs/workload-identity-federation),
|
|
85
|
-
[workforce identity federation](https://cloud.google.com/iam/docs/workforce-identity-federation), or a
|
|
86
|
-
[service account key](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-key).
|
|
87
|
-
|
|
88
|
-
Note: Service account keys are a security risk if not managed correctly. You should
|
|
89
|
-
[choose a more secure alternative to service account keys](https://cloud.google.com/docs/authentication#auth-decision-tree)
|
|
90
|
-
whenever possible.
|
|
91
|
-
|
|
92
|
-
The environment variables that google-cloud-apigee_registry
|
|
93
|
-
checks for credentials are:
|
|
94
|
-
|
|
95
|
-
* `GOOGLE_CLOUD_CREDENTIALS` - Path to JSON file, or JSON contents
|
|
96
|
-
* `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file
|
|
97
|
-
|
|
98
|
-
```ruby
|
|
99
|
-
require "google/cloud/apigee_registry"
|
|
100
|
-
|
|
101
|
-
ENV["GOOGLE_APPLICATION_CREDENTIALS"] = "path/to/credentialfile.json"
|
|
102
|
-
|
|
103
|
-
client = Google::Cloud::ApigeeRegistry.provisioning
|
|
104
|
-
```
|
|
105
|
-
|
|
106
|
-
### Local ADC file
|
|
107
|
-
|
|
108
|
-
You can set up a local ADC file with your user credentials for authentication during
|
|
109
|
-
development. If credentials are not provided in code or in environment variables,
|
|
110
|
-
then the local ADC credentials are discovered.
|
|
111
|
-
|
|
112
|
-
Follow the steps in [Quickstart](#quickstart) to set up a local ADC file.
|
|
113
|
-
|
|
114
|
-
### Google Cloud Platform environments
|
|
115
|
-
|
|
116
|
-
When running on Google Cloud Platform (GCP), including Google Compute Engine
|
|
117
|
-
(GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud
|
|
118
|
-
Functions (GCF) and Cloud Run, credentials are retrieved from the attached
|
|
119
|
-
service account automatically. Code should be written as if already authenticated.
|
|
120
|
-
|
|
121
|
-
For more information, see
|
|
122
|
-
[Set up ADC for Google Cloud services](https://cloud.google.com/docs/authentication/provide-credentials-adc#attached-sa).
|
|
@@ -1,227 +0,0 @@
|
|
|
1
|
-
# frozen_string_literal: true
|
|
2
|
-
|
|
3
|
-
# Copyright 2022 Google LLC
|
|
4
|
-
#
|
|
5
|
-
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
6
|
-
# you may not use this file except in compliance with the License.
|
|
7
|
-
# You may obtain a copy of the License at
|
|
8
|
-
#
|
|
9
|
-
# https://www.apache.org/licenses/LICENSE-2.0
|
|
10
|
-
#
|
|
11
|
-
# Unless required by applicable law or agreed to in writing, software
|
|
12
|
-
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
13
|
-
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
14
|
-
# See the License for the specific language governing permissions and
|
|
15
|
-
# limitations under the License.
|
|
16
|
-
|
|
17
|
-
# Auto-generated by gapic-generator-ruby. DO NOT EDIT!
|
|
18
|
-
|
|
19
|
-
# Require this file early so that the version constant gets defined before
|
|
20
|
-
# requiring "google/cloud". This is because google-cloud-core will load the
|
|
21
|
-
# entrypoint (gem name) file, which in turn re-requires this file (hence
|
|
22
|
-
# causing a require cycle) unless the version constant is already defined.
|
|
23
|
-
require "google/cloud/apigee_registry/version"
|
|
24
|
-
|
|
25
|
-
require "googleauth"
|
|
26
|
-
gem "google-cloud-core"
|
|
27
|
-
require "google/cloud" unless defined? ::Google::Cloud.new
|
|
28
|
-
require "google/cloud/config"
|
|
29
|
-
|
|
30
|
-
# Set the default configuration
|
|
31
|
-
::Google::Cloud.configure.add_config! :apigee_registry do |config|
|
|
32
|
-
config.add_field! :endpoint, nil, match: ::String
|
|
33
|
-
config.add_field! :credentials, nil, match: [::String, ::Hash, ::Google::Auth::Credentials]
|
|
34
|
-
config.add_field! :scope, nil, match: [::Array, ::String]
|
|
35
|
-
config.add_field! :lib_name, nil, match: ::String
|
|
36
|
-
config.add_field! :lib_version, nil, match: ::String
|
|
37
|
-
config.add_field! :interceptors, nil, match: ::Array
|
|
38
|
-
config.add_field! :timeout, nil, match: ::Numeric
|
|
39
|
-
config.add_field! :metadata, nil, match: ::Hash
|
|
40
|
-
config.add_field! :retry_policy, nil, match: [::Hash, ::Proc]
|
|
41
|
-
config.add_field! :quota_project, nil, match: ::String
|
|
42
|
-
config.add_field! :universe_domain, nil, match: ::String
|
|
43
|
-
end
|
|
44
|
-
|
|
45
|
-
module Google
|
|
46
|
-
module Cloud
|
|
47
|
-
module ApigeeRegistry
|
|
48
|
-
##
|
|
49
|
-
# Create a new client object for Provisioning.
|
|
50
|
-
#
|
|
51
|
-
# By default, this returns an instance of
|
|
52
|
-
# [Google::Cloud::ApigeeRegistry::V1::Provisioning::Client](https://cloud.google.com/ruby/docs/reference/google-cloud-apigee_registry-v1/latest/Google-Cloud-ApigeeRegistry-V1-Provisioning-Client)
|
|
53
|
-
# for a gRPC client for version V1 of the API.
|
|
54
|
-
# However, you can specify a different API version by passing it in the
|
|
55
|
-
# `version` parameter. If the Provisioning service is
|
|
56
|
-
# supported by that API version, and the corresponding gem is available, the
|
|
57
|
-
# appropriate versioned client will be returned.
|
|
58
|
-
# You can also specify a different transport by passing `:rest` or `:grpc` in
|
|
59
|
-
# the `transport` parameter.
|
|
60
|
-
#
|
|
61
|
-
# Raises an exception if the currently installed versioned client gem for the
|
|
62
|
-
# given API version does not support the given transport of the Provisioning service.
|
|
63
|
-
# You can determine whether the method will succeed by calling
|
|
64
|
-
# {Google::Cloud::ApigeeRegistry.provisioning_available?}.
|
|
65
|
-
#
|
|
66
|
-
# ## About Provisioning
|
|
67
|
-
#
|
|
68
|
-
# The service that is used for managing the data plane provisioning of the
|
|
69
|
-
# Registry.
|
|
70
|
-
#
|
|
71
|
-
# @param version [::String, ::Symbol] The API version to connect to. Optional.
|
|
72
|
-
# Defaults to `:v1`.
|
|
73
|
-
# @param transport [:grpc, :rest] The transport to use. Defaults to `:grpc`.
|
|
74
|
-
# @return [::Object] A client object for the specified version.
|
|
75
|
-
#
|
|
76
|
-
def self.provisioning version: :v1, transport: :grpc, &block
|
|
77
|
-
require "google/cloud/apigee_registry/#{version.to_s.downcase}"
|
|
78
|
-
|
|
79
|
-
package_name = Google::Cloud::ApigeeRegistry
|
|
80
|
-
.constants
|
|
81
|
-
.select { |sym| sym.to_s.downcase == version.to_s.downcase.tr("_", "") }
|
|
82
|
-
.first
|
|
83
|
-
service_module = Google::Cloud::ApigeeRegistry.const_get(package_name).const_get(:Provisioning)
|
|
84
|
-
service_module = service_module.const_get(:Rest) if transport == :rest
|
|
85
|
-
service_module.const_get(:Client).new(&block)
|
|
86
|
-
end
|
|
87
|
-
|
|
88
|
-
##
|
|
89
|
-
# Determines whether the Provisioning service is supported by the current client.
|
|
90
|
-
# If true, you can retrieve a client object by calling {Google::Cloud::ApigeeRegistry.provisioning}.
|
|
91
|
-
# If false, that method will raise an exception. This could happen if the given
|
|
92
|
-
# API version does not exist or does not support the Provisioning service,
|
|
93
|
-
# or if the versioned client gem needs an update to support the Provisioning service.
|
|
94
|
-
#
|
|
95
|
-
# @param version [::String, ::Symbol] The API version to connect to. Optional.
|
|
96
|
-
# Defaults to `:v1`.
|
|
97
|
-
# @param transport [:grpc, :rest] The transport to use. Defaults to `:grpc`.
|
|
98
|
-
# @return [boolean] Whether the service is available.
|
|
99
|
-
#
|
|
100
|
-
def self.provisioning_available? version: :v1, transport: :grpc
|
|
101
|
-
require "google/cloud/apigee_registry/#{version.to_s.downcase}"
|
|
102
|
-
package_name = Google::Cloud::ApigeeRegistry
|
|
103
|
-
.constants
|
|
104
|
-
.select { |sym| sym.to_s.downcase == version.to_s.downcase.tr("_", "") }
|
|
105
|
-
.first
|
|
106
|
-
return false unless package_name
|
|
107
|
-
service_module = Google::Cloud::ApigeeRegistry.const_get package_name
|
|
108
|
-
return false unless service_module.const_defined? :Provisioning
|
|
109
|
-
service_module = service_module.const_get :Provisioning
|
|
110
|
-
if transport == :rest
|
|
111
|
-
return false unless service_module.const_defined? :Rest
|
|
112
|
-
service_module = service_module.const_get :Rest
|
|
113
|
-
end
|
|
114
|
-
service_module.const_defined? :Client
|
|
115
|
-
rescue ::LoadError
|
|
116
|
-
false
|
|
117
|
-
end
|
|
118
|
-
|
|
119
|
-
##
|
|
120
|
-
# Create a new client object for Registry.
|
|
121
|
-
#
|
|
122
|
-
# By default, this returns an instance of
|
|
123
|
-
# [Google::Cloud::ApigeeRegistry::V1::Registry::Client](https://cloud.google.com/ruby/docs/reference/google-cloud-apigee_registry-v1/latest/Google-Cloud-ApigeeRegistry-V1-Registry-Client)
|
|
124
|
-
# for a gRPC client for version V1 of the API.
|
|
125
|
-
# However, you can specify a different API version by passing it in the
|
|
126
|
-
# `version` parameter. If the Registry service is
|
|
127
|
-
# supported by that API version, and the corresponding gem is available, the
|
|
128
|
-
# appropriate versioned client will be returned.
|
|
129
|
-
# You can also specify a different transport by passing `:rest` or `:grpc` in
|
|
130
|
-
# the `transport` parameter.
|
|
131
|
-
#
|
|
132
|
-
# Raises an exception if the currently installed versioned client gem for the
|
|
133
|
-
# given API version does not support the given transport of the Registry service.
|
|
134
|
-
# You can determine whether the method will succeed by calling
|
|
135
|
-
# {Google::Cloud::ApigeeRegistry.registry_available?}.
|
|
136
|
-
#
|
|
137
|
-
# ## About Registry
|
|
138
|
-
#
|
|
139
|
-
# The Registry service allows teams to manage descriptions of APIs.
|
|
140
|
-
#
|
|
141
|
-
# @param version [::String, ::Symbol] The API version to connect to. Optional.
|
|
142
|
-
# Defaults to `:v1`.
|
|
143
|
-
# @param transport [:grpc, :rest] The transport to use. Defaults to `:grpc`.
|
|
144
|
-
# @return [::Object] A client object for the specified version.
|
|
145
|
-
#
|
|
146
|
-
def self.registry version: :v1, transport: :grpc, &block
|
|
147
|
-
require "google/cloud/apigee_registry/#{version.to_s.downcase}"
|
|
148
|
-
|
|
149
|
-
package_name = Google::Cloud::ApigeeRegistry
|
|
150
|
-
.constants
|
|
151
|
-
.select { |sym| sym.to_s.downcase == version.to_s.downcase.tr("_", "") }
|
|
152
|
-
.first
|
|
153
|
-
service_module = Google::Cloud::ApigeeRegistry.const_get(package_name).const_get(:Registry)
|
|
154
|
-
service_module = service_module.const_get(:Rest) if transport == :rest
|
|
155
|
-
service_module.const_get(:Client).new(&block)
|
|
156
|
-
end
|
|
157
|
-
|
|
158
|
-
##
|
|
159
|
-
# Determines whether the Registry service is supported by the current client.
|
|
160
|
-
# If true, you can retrieve a client object by calling {Google::Cloud::ApigeeRegistry.registry}.
|
|
161
|
-
# If false, that method will raise an exception. This could happen if the given
|
|
162
|
-
# API version does not exist or does not support the Registry service,
|
|
163
|
-
# or if the versioned client gem needs an update to support the Registry service.
|
|
164
|
-
#
|
|
165
|
-
# @param version [::String, ::Symbol] The API version to connect to. Optional.
|
|
166
|
-
# Defaults to `:v1`.
|
|
167
|
-
# @param transport [:grpc, :rest] The transport to use. Defaults to `:grpc`.
|
|
168
|
-
# @return [boolean] Whether the service is available.
|
|
169
|
-
#
|
|
170
|
-
def self.registry_available? version: :v1, transport: :grpc
|
|
171
|
-
require "google/cloud/apigee_registry/#{version.to_s.downcase}"
|
|
172
|
-
package_name = Google::Cloud::ApigeeRegistry
|
|
173
|
-
.constants
|
|
174
|
-
.select { |sym| sym.to_s.downcase == version.to_s.downcase.tr("_", "") }
|
|
175
|
-
.first
|
|
176
|
-
return false unless package_name
|
|
177
|
-
service_module = Google::Cloud::ApigeeRegistry.const_get package_name
|
|
178
|
-
return false unless service_module.const_defined? :Registry
|
|
179
|
-
service_module = service_module.const_get :Registry
|
|
180
|
-
if transport == :rest
|
|
181
|
-
return false unless service_module.const_defined? :Rest
|
|
182
|
-
service_module = service_module.const_get :Rest
|
|
183
|
-
end
|
|
184
|
-
service_module.const_defined? :Client
|
|
185
|
-
rescue ::LoadError
|
|
186
|
-
false
|
|
187
|
-
end
|
|
188
|
-
|
|
189
|
-
##
|
|
190
|
-
# Configure the google-cloud-apigee_registry library.
|
|
191
|
-
#
|
|
192
|
-
# The following configuration parameters are supported:
|
|
193
|
-
#
|
|
194
|
-
# * `credentials` (*type:* `String, Hash, Google::Auth::Credentials`) -
|
|
195
|
-
# The path to the keyfile as a String, the contents of the keyfile as a
|
|
196
|
-
# Hash, or a Google::Auth::Credentials object.
|
|
197
|
-
# * `lib_name` (*type:* `String`) -
|
|
198
|
-
# The library name as recorded in instrumentation and logging.
|
|
199
|
-
# * `lib_version` (*type:* `String`) -
|
|
200
|
-
# The library version as recorded in instrumentation and logging.
|
|
201
|
-
# * `interceptors` (*type:* `Array<GRPC::ClientInterceptor>`) -
|
|
202
|
-
# An array of interceptors that are run before calls are executed.
|
|
203
|
-
# * `timeout` (*type:* `Numeric`) -
|
|
204
|
-
# Default timeout in seconds.
|
|
205
|
-
# * `metadata` (*type:* `Hash{Symbol=>String}`) -
|
|
206
|
-
# Additional headers to be sent with the call.
|
|
207
|
-
# * `retry_policy` (*type:* `Hash`) -
|
|
208
|
-
# The retry policy. The value is a hash with the following keys:
|
|
209
|
-
# * `:initial_delay` (*type:* `Numeric`) - The initial delay in seconds.
|
|
210
|
-
# * `:max_delay` (*type:* `Numeric`) - The max delay in seconds.
|
|
211
|
-
# * `:multiplier` (*type:* `Numeric`) - The incremental backoff multiplier.
|
|
212
|
-
# * `:retry_codes` (*type:* `Array<String>`) -
|
|
213
|
-
# The error codes that should trigger a retry.
|
|
214
|
-
#
|
|
215
|
-
# @return [::Google::Cloud::Config] The default configuration used by this library
|
|
216
|
-
#
|
|
217
|
-
def self.configure
|
|
218
|
-
yield ::Google::Cloud.configure.apigee_registry if block_given?
|
|
219
|
-
|
|
220
|
-
::Google::Cloud.configure.apigee_registry
|
|
221
|
-
end
|
|
222
|
-
end
|
|
223
|
-
end
|
|
224
|
-
end
|
|
225
|
-
|
|
226
|
-
helper_path = ::File.join __dir__, "apigee_registry", "helpers.rb"
|
|
227
|
-
require "google/cloud/apigee_registry/helpers" if ::File.file? helper_path
|
|
@@ -1,19 +0,0 @@
|
|
|
1
|
-
# frozen_string_literal: true
|
|
2
|
-
|
|
3
|
-
# Copyright 2022 Google LLC
|
|
4
|
-
#
|
|
5
|
-
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
6
|
-
# you may not use this file except in compliance with the License.
|
|
7
|
-
# You may obtain a copy of the License at
|
|
8
|
-
#
|
|
9
|
-
# https://www.apache.org/licenses/LICENSE-2.0
|
|
10
|
-
#
|
|
11
|
-
# Unless required by applicable law or agreed to in writing, software
|
|
12
|
-
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
13
|
-
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
14
|
-
# See the License for the specific language governing permissions and
|
|
15
|
-
# limitations under the License.
|
|
16
|
-
|
|
17
|
-
# Auto-generated by gapic-generator-ruby. DO NOT EDIT!
|
|
18
|
-
|
|
19
|
-
require "google/cloud/apigee_registry" unless defined? Google::Cloud::ApigeeRegistry::VERSION
|