google-cloud-alloy_db 1.2.0 → 2.0.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +34 -5
- data/lib/google/cloud/alloy_db/version.rb +1 -1
- data/lib/google/cloud/alloy_db.rb +36 -0
- metadata +10 -39
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 214c763bf1548c0652ac061df920fea6ad514ad03dce458f41f8b7db6209a1ca
|
|
4
|
+
data.tar.gz: 72ee5519d19d9b13841431811caa714a438b60f1e2573d9275f15b7ef8177b16
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: fe3a25b27743e77f0750034a00503759082c968800d966ebdb504588454caafd5cf65ddd412fafaf8fdb93ed979defd279c66689c196ece5bbce4fa46948d822
|
|
7
|
+
data.tar.gz: 3c0aeac2780b6f0aed8c87f988fea379368a8d78eb646e937963e22132ebfddad761f6eb11f50e10aaa5074ec2349d7ced00b5041d0cdd6ea917a28a9c57ec51
|
data/README.md
CHANGED
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
# Ruby Client for the AlloyDB API
|
|
2
2
|
|
|
3
|
-
AlloyDB for PostgreSQL is an open source-compatible database service that provides a powerful option for migrating, modernizing, or building commercial-grade applications. It offers full compatibility with standard PostgreSQL, and is more than 4x faster for transactional workloads and up to 100x faster for analytical queries than standard PostgreSQL in our performance tests. AlloyDB for PostgreSQL offers a 99.99 percent availability SLA inclusive of maintenance.
|
|
3
|
+
AlloyDB for PostgreSQL is an open source-compatible database service that provides a powerful option for migrating, modernizing, or building commercial-grade applications. It offers full compatibility with standard PostgreSQL, and is more than 4x faster for transactional workloads and up to 100x faster for analytical queries than standard PostgreSQL in our performance tests. AlloyDB for PostgreSQL offers a 99.99 percent availability SLA inclusive of maintenance. AlloyDB is optimized for the most demanding use cases, allowing you to build new applications that require high transaction throughput, large database sizes, or multiple read resources; scale existing PostgreSQL workloads with no application changes; and modernize legacy proprietary databases.
|
|
4
4
|
|
|
5
|
-
AlloyDB for PostgreSQL is an open source-compatible database service that provides a powerful option for migrating, modernizing, or building commercial-grade applications. It offers full compatibility with standard PostgreSQL, and is more than 4x faster for transactional workloads and up to 100x faster for analytical queries than standard PostgreSQL in our performance tests. AlloyDB for PostgreSQL offers a 99.99 percent availability SLA inclusive of maintenance.
|
|
5
|
+
AlloyDB for PostgreSQL is an open source-compatible database service that provides a powerful option for migrating, modernizing, or building commercial-grade applications. It offers full compatibility with standard PostgreSQL, and is more than 4x faster for transactional workloads and up to 100x faster for analytical queries than standard PostgreSQL in our performance tests. AlloyDB for PostgreSQL offers a 99.99 percent availability SLA inclusive of maintenance. AlloyDB is optimized for the most demanding use cases, allowing you to build new applications that require high transaction throughput, large database sizes, or multiple read resources; scale existing PostgreSQL workloads with no application changes; and modernize legacy proprietary databases.
|
|
6
6
|
|
|
7
7
|
Actual client classes for the various versions of this API are defined in
|
|
8
8
|
_versioned_ client gems, with names of the form `google-cloud-alloy_db-v*`.
|
|
@@ -16,8 +16,7 @@ for this library, google-cloud-alloy_db, to see the convenience methods for
|
|
|
16
16
|
constructing client objects. Reference documentation for the client objects
|
|
17
17
|
themselves can be found in the client library documentation for the versioned
|
|
18
18
|
client gems:
|
|
19
|
-
[google-cloud-alloy_db-v1](https://cloud.google.com/ruby/docs/reference/google-cloud-alloy_db-v1/latest)
|
|
20
|
-
[google-cloud-alloy_db-v1beta](https://cloud.google.com/ruby/docs/reference/google-cloud-alloy_db-v1beta/latest).
|
|
19
|
+
[google-cloud-alloy_db-v1](https://cloud.google.com/ruby/docs/reference/google-cloud-alloy_db-v1/latest).
|
|
21
20
|
|
|
22
21
|
See also the [Product Documentation](https://cloud.google.com/alloydb/docs)
|
|
23
22
|
for more usage information.
|
|
@@ -35,9 +34,39 @@ In order to use this library, you first need to go through the following steps:
|
|
|
35
34
|
1. [Enable the API.](https://console.cloud.google.com/apis/library/alloydb.googleapis.com)
|
|
36
35
|
1. {file:AUTHENTICATION.md Set up authentication.}
|
|
37
36
|
|
|
37
|
+
## Debug Logging
|
|
38
|
+
|
|
39
|
+
This library comes with opt-in Debug Logging that can help you troubleshoot
|
|
40
|
+
your application's integration with the API. When logging is activated, key
|
|
41
|
+
events such as requests and responses, along with data payloads and metadata
|
|
42
|
+
such as headers and client configuration, are logged to the standard error
|
|
43
|
+
stream.
|
|
44
|
+
|
|
45
|
+
**WARNING:** Client Library Debug Logging includes your data payloads in
|
|
46
|
+
plaintext, which could include sensitive data such as PII for yourself or your
|
|
47
|
+
customers, private keys, or other security data that could be compromising if
|
|
48
|
+
leaked. Always practice good data hygiene with your application logs, and follow
|
|
49
|
+
the principle of least access. Google also recommends that Client Library Debug
|
|
50
|
+
Logging be enabled only temporarily during active debugging, and not used
|
|
51
|
+
permanently in production.
|
|
52
|
+
|
|
53
|
+
To enable logging, set the environment variable `GOOGLE_SDK_RUBY_LOGGING_GEMS`
|
|
54
|
+
to the value `all`. Alternatively, you can set the value to a comma-delimited
|
|
55
|
+
list of client library gem names. This will select the default logging behavior,
|
|
56
|
+
which writes logs to the standard error stream. On a local workstation, this may
|
|
57
|
+
result in logs appearing on the console. When running on a Google Cloud hosting
|
|
58
|
+
service such as [Google Cloud Run](https://cloud.google.com/run), this generally
|
|
59
|
+
results in logs appearing alongside your application logs in the
|
|
60
|
+
[Google Cloud Logging](https://cloud.google.com/logging/) service.
|
|
61
|
+
|
|
62
|
+
Debug logging also requires that the versioned clients for this service be
|
|
63
|
+
sufficiently recent, released after about Dec 10, 2024. If logging is not
|
|
64
|
+
working, try updating the versioned clients in your bundle or installed gems:
|
|
65
|
+
[google-cloud-alloy_db-v1](https://cloud.google.com/ruby/docs/reference/google-cloud-alloy_db-v1/latest).
|
|
66
|
+
|
|
38
67
|
## Supported Ruby Versions
|
|
39
68
|
|
|
40
|
-
This library is supported on Ruby
|
|
69
|
+
This library is supported on Ruby 3.0+.
|
|
41
70
|
|
|
42
71
|
Google provides official support for Ruby versions that are actively supported
|
|
43
72
|
by Ruby Core—that is, Ruby versions that are either in normal maintenance or
|
|
@@ -58,6 +58,11 @@ module Google
|
|
|
58
58
|
# You can also specify a different transport by passing `:rest` or `:grpc` in
|
|
59
59
|
# the `transport` parameter.
|
|
60
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 AlloyDBAdmin service.
|
|
63
|
+
# You can determine whether the method will succeed by calling
|
|
64
|
+
# {Google::Cloud::AlloyDB.alloy_db_admin_available?}.
|
|
65
|
+
#
|
|
61
66
|
# ## About AlloyDBAdmin
|
|
62
67
|
#
|
|
63
68
|
# Service describing handlers for resources
|
|
@@ -79,6 +84,37 @@ module Google
|
|
|
79
84
|
service_module.const_get(:Client).new(&block)
|
|
80
85
|
end
|
|
81
86
|
|
|
87
|
+
##
|
|
88
|
+
# Determines whether the AlloyDBAdmin service is supported by the current client.
|
|
89
|
+
# If true, you can retrieve a client object by calling {Google::Cloud::AlloyDB.alloy_db_admin}.
|
|
90
|
+
# If false, that method will raise an exception. This could happen if the given
|
|
91
|
+
# API version does not exist or does not support the AlloyDBAdmin service,
|
|
92
|
+
# or if the versioned client gem needs an update to support the AlloyDBAdmin service.
|
|
93
|
+
#
|
|
94
|
+
# @param version [::String, ::Symbol] The API version to connect to. Optional.
|
|
95
|
+
# Defaults to `:v1`.
|
|
96
|
+
# @param transport [:grpc, :rest] The transport to use. Defaults to `:grpc`.
|
|
97
|
+
# @return [boolean] Whether the service is available.
|
|
98
|
+
#
|
|
99
|
+
def self.alloy_db_admin_available? version: :v1, transport: :grpc
|
|
100
|
+
require "google/cloud/alloy_db/#{version.to_s.downcase}"
|
|
101
|
+
package_name = Google::Cloud::AlloyDB
|
|
102
|
+
.constants
|
|
103
|
+
.select { |sym| sym.to_s.downcase == version.to_s.downcase.tr("_", "") }
|
|
104
|
+
.first
|
|
105
|
+
return false unless package_name
|
|
106
|
+
service_module = Google::Cloud::AlloyDB.const_get package_name
|
|
107
|
+
return false unless service_module.const_defined? :AlloyDBAdmin
|
|
108
|
+
service_module = service_module.const_get :AlloyDBAdmin
|
|
109
|
+
if transport == :rest
|
|
110
|
+
return false unless service_module.const_defined? :Rest
|
|
111
|
+
service_module = service_module.const_get :Rest
|
|
112
|
+
end
|
|
113
|
+
service_module.const_defined? :Client
|
|
114
|
+
rescue ::LoadError
|
|
115
|
+
false
|
|
116
|
+
end
|
|
117
|
+
|
|
82
118
|
##
|
|
83
119
|
# Configure the google-cloud-alloy_db library.
|
|
84
120
|
#
|
metadata
CHANGED
|
@@ -1,55 +1,28 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: google-cloud-alloy_db
|
|
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
|
-
autorequire:
|
|
9
8
|
bindir: bin
|
|
10
9
|
cert_chain: []
|
|
11
|
-
date:
|
|
10
|
+
date: 2025-02-13 00:00:00.000000000 Z
|
|
12
11
|
dependencies:
|
|
13
12
|
- !ruby/object:Gem::Dependency
|
|
14
13
|
name: google-cloud-alloy_db-v1
|
|
15
14
|
requirement: !ruby/object:Gem::Requirement
|
|
16
15
|
requirements:
|
|
17
|
-
- - "
|
|
18
|
-
- !ruby/object:Gem::Version
|
|
19
|
-
version: '0.8'
|
|
20
|
-
- - "<"
|
|
21
|
-
- !ruby/object:Gem::Version
|
|
22
|
-
version: 2.a
|
|
23
|
-
type: :runtime
|
|
24
|
-
prerelease: false
|
|
25
|
-
version_requirements: !ruby/object:Gem::Requirement
|
|
26
|
-
requirements:
|
|
27
|
-
- - ">="
|
|
28
|
-
- !ruby/object:Gem::Version
|
|
29
|
-
version: '0.8'
|
|
30
|
-
- - "<"
|
|
31
|
-
- !ruby/object:Gem::Version
|
|
32
|
-
version: 2.a
|
|
33
|
-
- !ruby/object:Gem::Dependency
|
|
34
|
-
name: google-cloud-alloy_db-v1beta
|
|
35
|
-
requirement: !ruby/object:Gem::Requirement
|
|
36
|
-
requirements:
|
|
37
|
-
- - ">="
|
|
38
|
-
- !ruby/object:Gem::Version
|
|
39
|
-
version: '0.6'
|
|
40
|
-
- - "<"
|
|
16
|
+
- - "~>"
|
|
41
17
|
- !ruby/object:Gem::Version
|
|
42
|
-
version:
|
|
18
|
+
version: '1.0'
|
|
43
19
|
type: :runtime
|
|
44
20
|
prerelease: false
|
|
45
21
|
version_requirements: !ruby/object:Gem::Requirement
|
|
46
22
|
requirements:
|
|
47
|
-
- - "
|
|
48
|
-
- !ruby/object:Gem::Version
|
|
49
|
-
version: '0.6'
|
|
50
|
-
- - "<"
|
|
23
|
+
- - "~>"
|
|
51
24
|
- !ruby/object:Gem::Version
|
|
52
|
-
version:
|
|
25
|
+
version: '1.0'
|
|
53
26
|
- !ruby/object:Gem::Dependency
|
|
54
27
|
name: google-cloud-core
|
|
55
28
|
requirement: !ruby/object:Gem::Requirement
|
|
@@ -69,7 +42,7 @@ description: AlloyDB for PostgreSQL is an open source-compatible database servic
|
|
|
69
42
|
applications. It offers full compatibility with standard PostgreSQL, and is more
|
|
70
43
|
than 4x faster for transactional workloads and up to 100x faster for analytical
|
|
71
44
|
queries than standard PostgreSQL in our performance tests. AlloyDB for PostgreSQL
|
|
72
|
-
offers a 99.99 percent availability SLA inclusive of maintenance.
|
|
45
|
+
offers a 99.99 percent availability SLA inclusive of maintenance. AlloyDB is optimized
|
|
73
46
|
for the most demanding use cases, allowing you to build new applications that require
|
|
74
47
|
high transaction throughput, large database sizes, or multiple read resources; scale
|
|
75
48
|
existing PostgreSQL workloads with no application changes; and modernize legacy
|
|
@@ -90,7 +63,6 @@ homepage: https://github.com/googleapis/google-cloud-ruby
|
|
|
90
63
|
licenses:
|
|
91
64
|
- Apache-2.0
|
|
92
65
|
metadata: {}
|
|
93
|
-
post_install_message:
|
|
94
66
|
rdoc_options: []
|
|
95
67
|
require_paths:
|
|
96
68
|
- lib
|
|
@@ -98,22 +70,21 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
|
98
70
|
requirements:
|
|
99
71
|
- - ">="
|
|
100
72
|
- !ruby/object:Gem::Version
|
|
101
|
-
version: '
|
|
73
|
+
version: '3.0'
|
|
102
74
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
|
103
75
|
requirements:
|
|
104
76
|
- - ">="
|
|
105
77
|
- !ruby/object:Gem::Version
|
|
106
78
|
version: '0'
|
|
107
79
|
requirements: []
|
|
108
|
-
rubygems_version: 3.
|
|
109
|
-
signing_key:
|
|
80
|
+
rubygems_version: 3.6.3
|
|
110
81
|
specification_version: 4
|
|
111
82
|
summary: AlloyDB for PostgreSQL is an open source-compatible database service that
|
|
112
83
|
provides a powerful option for migrating, modernizing, or building commercial-grade
|
|
113
84
|
applications. It offers full compatibility with standard PostgreSQL, and is more
|
|
114
85
|
than 4x faster for transactional workloads and up to 100x faster for analytical
|
|
115
86
|
queries than standard PostgreSQL in our performance tests. AlloyDB for PostgreSQL
|
|
116
|
-
offers a 99.99 percent availability SLA inclusive of maintenance.
|
|
87
|
+
offers a 99.99 percent availability SLA inclusive of maintenance. AlloyDB is optimized
|
|
117
88
|
for the most demanding use cases, allowing you to build new applications that require
|
|
118
89
|
high transaction throughput, large database sizes, or multiple read resources; scale
|
|
119
90
|
existing PostgreSQL workloads with no application changes; and modernize legacy
|