@maxim_mazurok/gapi.client.sqladmin-v1beta4 0.0.20231011 → 0.0.20231017

package/index.d.ts

@@ -9,7 +9,7 @@
 // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
 // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
 // Generated from: https://sqladmin.googleapis.com/$discovery/rest?version=v1beta4
-// Revision: 20231011
+// Revision: 20231017
 
 /// <reference types="gapi.client" />
 
@@ -734,10 +734,13 @@ declare namespace gapi.client {
                      */
                     recoveryOnly?:
                         boolean;
-                    /** Optional. StopAt keyword for transaction log import, Applies to Cloud SQL for SQL Server only */
+                    /**
+                     * Optional. The timestamp when the import should stop. This timestamp is in the [RFC 3339](https://tools.ietf.org/html/rfc3339) format (for example,
+                     * `2023-10-01T16:19:00.094`). This field is equivalent to the STOPAT keyword and applies to Cloud SQL for SQL Server only.
+                     */
                     stopAt?:
                         string;
-                    /** Optional. StopAtMark keyword for transaction log import, Applies to Cloud SQL for SQL Server only */
+                    /** Optional. The marked transaction where the import should stop. This field is equivalent to the STOPATMARK keyword and applies to Cloud SQL for SQL Server only. */
                     stopAtMark?:
                         string;
                     /** Whether or not the backup set being restored is striped. Applies only to Cloud SQL for SQL Server. */
@@ -918,20 +921,19 @@ declare namespace gapi.client {
             pscConfig?:
                 PscConfig;
             /**
-             * LINT.IfChange(require_ssl_deprecate) Whether SSL/TLS connections over IP are enforced or not. If set to false, allow both non-SSL/non-TLS and SSL/TLS connections. For SSL/TLS
-             * connections, the client certificate will not be verified. If set to true, only allow connections encrypted with SSL/TLS and with valid client certificates. If you want to enforce
-             * SSL/TLS without enforcing the requirement for valid client certificates, use the `ssl_mode` flag instead of the legacy `require_ssl` flag.
-             * LINT.ThenChange(//depot/google3/java/com/google/storage/speckle/boss/admin/actions/InstanceUpdateAction.java:update_api_temp_fix)
+             * Whether SSL/TLS connections over IP are enforced. If set to false, then allow both non-SSL/non-TLS and SSL/TLS connections. For SSL/TLS connections, the client certificate won't be
+             * verified. If set to true, then only allow connections encrypted with SSL/TLS and with valid client certificates. If you want to enforce SSL/TLS without enforcing the requirement for
+             * valid client certificates, then use the `ssl_mode` flag instead of the legacy `require_ssl` flag.
              */
             requireSsl?:
                 boolean;
             /**
-             * Specify how SSL/TLS will be enforced in database connections. This flag is only supported for PostgreSQL. Use the legacy `require_ssl` flag for enforcing SSL/TLS in MySQL and SQL
-             * Server. But, for PostgreSQL, it is recommended to use the `ssl_mode` flag instead of the legacy `require_ssl` flag. To avoid the conflict between those flags in PostgreSQL, only the
-             * following value pairs are valid: ssl_mode=ALLOW_UNENCRYPTED_AND_ENCRYPTED, require_ssl=false; ssl_mode=ENCRYPTED_ONLY, require_ssl=false;
-             * ssl_mode=TRUSTED_CLIENT_CERTIFICATE_REQUIRED, require_ssl=true; Note that the value of `ssl_mode` gets priority over the value of the legacy `require_ssl`. For example, for the pair
-             * `ssl_mode=ENCRYPTED_ONLY, require_ssl=false`, the `ssl_mode=ENCRYPTED_ONLY` means "only accepts SSL connection", while the `require_ssl=false` means "both non-SSL and SSL
-             * connections are allowed". The database will respect `ssl_mode` in this case and only accept SSL connections.
+             * Specify how SSL/TLS is enforced in database connections. This flag is supported only for PostgreSQL. Use the legacy `require_ssl` flag for enforcing SSL/TLS in MySQL and SQL Server.
+             * But, for PostgreSQL, use the `ssl_mode` flag instead of the legacy `require_ssl` flag. To avoid the conflict between those flags in PostgreSQL, only the following value pairs are
+             * valid: * `ssl_mode=ALLOW_UNENCRYPTED_AND_ENCRYPTED` and `require_ssl=false` * `ssl_mode=ENCRYPTED_ONLY` and `require_ssl=false` * `ssl_mode=TRUSTED_CLIENT_CERTIFICATE_REQUIRED` and
+             * `require_ssl=true` Note that the value of `ssl_mode` gets priority over the value of the legacy `require_ssl`. For example, for the pair `ssl_mode=ENCRYPTED_ONLY,
+             * require_ssl=false`, the `ssl_mode=ENCRYPTED_ONLY` means "only accepts SSL connection", while the `require_ssl=false` means "both non-SSL and SSL connections are allowed". The
+             * database respects `ssl_mode` in this case and only accepts SSL connections.
              */
             sslMode?:
                 string;
@@ -1173,9 +1175,6 @@ declare namespace gapi.client {
             /** The complexity of the password. */
             complexity?:
                 string;
-            /** Disallow credentials that have been previously compromised by a public data breach. */
-            disallowCompromisedCredentials?:
-                boolean;
             /** Disallow username as a part of the password. */
             disallowUsernameSubstring?:
                 boolean;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maxim_mazurok/gapi.client.sqladmin-v1beta4",
-  "version": "0.0.20231011",
+  "version": "0.0.20231017",
   "description": "TypeScript typings for Cloud SQL Admin API v1beta4",
   "license": "MIT",
   "author": {

package/tests.ts

@@ -3,7 +3,7 @@
 // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
 // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
 
-// Revision: 20231011
+// Revision: 20231017
 
 gapi.load('client', async () => {
     /** now we can use gapi.client */
@@ -533,7 +533,6 @@ gapi.load('client', async () => {
                 },
                 passwordValidationPolicy: {
                     complexity: "Test string",
-                    disallowCompromisedCredentials: true,
                     disallowUsernameSubstring: true,
                     enablePasswordPolicy: true,
                     minLength: 42,
@@ -782,7 +781,6 @@ gapi.load('client', async () => {
                 },
                 passwordValidationPolicy: {
                     complexity: "Test string",
-                    disallowCompromisedCredentials: true,
                     disallowUsernameSubstring: true,
                     enablePasswordPolicy: true,
                     minLength: 42,
@@ -1090,7 +1088,6 @@ gapi.load('client', async () => {
                 },
                 passwordValidationPolicy: {
                     complexity: "Test string",
-                    disallowCompromisedCredentials: true,
                     disallowUsernameSubstring: true,
                     enablePasswordPolicy: true,
                     minLength: 42,