google-cloud-alloy_db 1.2.0 → 1.3.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 0ccdff024b13ae649757cf698da1c41b77a2b5250b08f6f044a413706fb27d50
4
- data.tar.gz: 0b1cde820d81d25fccad3eb04d3055fe7a9e26bf936202e13c7a986172f99c4f
3
+ metadata.gz: fb7aea5e22b66e2d21f46d657152a665790c7e0fe2e9559d29a938c3e9182a14
4
+ data.tar.gz: 323c1470052f76401250c273365a6af606faa1200561867398863d3e1fae90a3
5
5
  SHA512:
6
- metadata.gz: 28e7bde833c2325c28beba3f903b5db18e0c704bb67cf2cb77e7f8cd596987d6c42ba5f6903cd39126adf2b813ed2d5af0b516bb9ebf7c3139c1ad940e9a6699
7
- data.tar.gz: fc8558e1d969d4e08095e7228ae2b5c50e36412b23a19f3108e9f5786095fba519664cf05de8b42dda358fb3e9313ce104ad7b698530b68ff00e6a958b7eec8a
6
+ metadata.gz: 1835aca2b2359a90668921e6508a2ad55f2707c1310febbacfe50771c6daed14c4bcb676d271c59c292d09f9f6d6f376359c49101d52e9faaf60c31df77c8940
7
+ data.tar.gz: d5d8d3957844d573ff5c114e6ac993ebc1a27e0f6d92140e5a2da4b1878768d045f575742672fa60170893e078dd53ae2723e2c9ce24dbe30a619bb971b5dbfb
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. 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.
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. 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.
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*`.
@@ -35,9 +35,40 @@ In order to use this library, you first need to go through the following steps:
35
35
  1. [Enable the API.](https://console.cloud.google.com/apis/library/alloydb.googleapis.com)
36
36
  1. {file:AUTHENTICATION.md Set up authentication.}
37
37
 
38
+ ## Debug Logging
39
+
40
+ This library comes with opt-in Debug Logging that can help you troubleshoot
41
+ your application's integration with the API. When logging is activated, key
42
+ events such as requests and responses, along with data payloads and metadata
43
+ such as headers and client configuration, are logged to the standard error
44
+ stream.
45
+
46
+ **WARNING:** Client Library Debug Logging includes your data payloads in
47
+ plaintext, which could include sensitive data such as PII for yourself or your
48
+ customers, private keys, or other security data that could be compromising if
49
+ leaked. Always practice good data hygiene with your application logs, and follow
50
+ the principle of least access. Google also recommends that Client Library Debug
51
+ Logging be enabled only temporarily during active debugging, and not used
52
+ permanently in production.
53
+
54
+ To enable logging, set the environment variable `GOOGLE_SDK_RUBY_LOGGING_GEMS`
55
+ to the value `all`. Alternatively, you can set the value to a comma-delimited
56
+ list of client library gem names. This will select the default logging behavior,
57
+ which writes logs to the standard error stream. On a local workstation, this may
58
+ result in logs appearing on the console. When running on a Google Cloud hosting
59
+ service such as [Google Cloud Run](https://cloud.google.com/run), this generally
60
+ results in logs appearing alongside your application logs in the
61
+ [Google Cloud Logging](https://cloud.google.com/logging/) service.
62
+
63
+ Debug logging also requires that the versioned clients for this service be
64
+ sufficiently recent, released after about Dec 10, 2024. If logging is not
65
+ working, try updating the versioned clients in your bundle or installed gems:
66
+ [google-cloud-alloy_db-v1](https://cloud.google.com/ruby/docs/reference/google-cloud-alloy_db-v1/latest),
67
+ [google-cloud-alloy_db-v1beta](https://cloud.google.com/ruby/docs/reference/google-cloud-alloy_db-v1beta/latest).
68
+
38
69
  ## Supported Ruby Versions
39
70
 
40
- This library is supported on Ruby 2.7+.
71
+ This library is supported on Ruby 3.0+.
41
72
 
42
73
  Google provides official support for Ruby versions that are actively supported
43
74
  by Ruby Core—that is, Ruby versions that are either in normal maintenance or
@@ -20,7 +20,7 @@
20
20
  module Google
21
21
  module Cloud
22
22
  module AlloyDB
23
- VERSION = "1.2.0"
23
+ VERSION = "1.3.0"
24
24
  end
25
25
  end
26
26
  end
@@ -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,14 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-cloud-alloy_db
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.2.0
4
+ version: 1.3.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Google LLC
8
- autorequire:
9
8
  bindir: bin
10
9
  cert_chain: []
11
- date: 2024-02-26 00:00:00.000000000 Z
10
+ date: 2025-01-29 00:00:00.000000000 Z
12
11
  dependencies:
13
12
  - !ruby/object:Gem::Dependency
14
13
  name: google-cloud-alloy_db-v1
@@ -69,7 +68,7 @@ description: AlloyDB for PostgreSQL is an open source-compatible database servic
69
68
  applications. It offers full compatibility with standard PostgreSQL, and is more
70
69
  than 4x faster for transactional workloads and up to 100x faster for analytical
71
70
  queries than standard PostgreSQL in our performance tests. AlloyDB for PostgreSQL
72
- offers a 99.99 percent availability SLA inclusive of maintenance. AlloyDB is optimized
71
+ offers a 99.99 percent availability SLA inclusive of maintenance. AlloyDB is optimized
73
72
  for the most demanding use cases, allowing you to build new applications that require
74
73
  high transaction throughput, large database sizes, or multiple read resources; scale
75
74
  existing PostgreSQL workloads with no application changes; and modernize legacy
@@ -90,7 +89,6 @@ homepage: https://github.com/googleapis/google-cloud-ruby
90
89
  licenses:
91
90
  - Apache-2.0
92
91
  metadata: {}
93
- post_install_message:
94
92
  rdoc_options: []
95
93
  require_paths:
96
94
  - lib
@@ -98,22 +96,21 @@ required_ruby_version: !ruby/object:Gem::Requirement
98
96
  requirements:
99
97
  - - ">="
100
98
  - !ruby/object:Gem::Version
101
- version: '2.7'
99
+ version: '3.0'
102
100
  required_rubygems_version: !ruby/object:Gem::Requirement
103
101
  requirements:
104
102
  - - ">="
105
103
  - !ruby/object:Gem::Version
106
104
  version: '0'
107
105
  requirements: []
108
- rubygems_version: 3.5.6
109
- signing_key:
106
+ rubygems_version: 3.6.2
110
107
  specification_version: 4
111
108
  summary: AlloyDB for PostgreSQL is an open source-compatible database service that
112
109
  provides a powerful option for migrating, modernizing, or building commercial-grade
113
110
  applications. It offers full compatibility with standard PostgreSQL, and is more
114
111
  than 4x faster for transactional workloads and up to 100x faster for analytical
115
112
  queries than standard PostgreSQL in our performance tests. AlloyDB for PostgreSQL
116
- offers a 99.99 percent availability SLA inclusive of maintenance. AlloyDB is optimized
113
+ offers a 99.99 percent availability SLA inclusive of maintenance. AlloyDB is optimized
117
114
  for the most demanding use cases, allowing you to build new applications that require
118
115
  high transaction throughput, large database sizes, or multiple read resources; scale
119
116
  existing PostgreSQL workloads with no application changes; and modernize legacy