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

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.
Files changed (3) hide show
  1. package/index.d.ts +15 -16
  2. package/package.json +1 -1
  3. package/tests.ts +1 -4
package/index.d.ts CHANGED
@@ -9,7 +9,7 @@
9
9
  // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
10
10
  // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
11
11
  // Generated from: https://sqladmin.googleapis.com/$discovery/rest?version=v1
12
- // Revision: 20231011
12
+ // Revision: 20231017
13
13
 
14
14
  /// <reference types="gapi.client" />
15
15
 
@@ -734,10 +734,13 @@ declare namespace gapi.client {
734
734
  */
735
735
  recoveryOnly?:
736
736
  boolean;
737
- /** Optional. StopAt keyword for transaction log import, Applies to Cloud SQL for SQL Server only */
737
+ /**
738
+ * Optional. The timestamp when the import should stop. This timestamp is in the [RFC 3339](https://tools.ietf.org/html/rfc3339) format (for example,
739
+ * `2023-10-01T16:19:00.094`). This field is equivalent to the STOPAT keyword and applies to Cloud SQL for SQL Server only.
740
+ */
738
741
  stopAt?:
739
742
  string;
740
- /** Optional. StopAtMark keyword for transaction log import, Applies to Cloud SQL for SQL Server only */
743
+ /** 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. */
741
744
  stopAtMark?:
742
745
  string;
743
746
  /** Whether or not the backup set being restored is striped. Applies only to Cloud SQL for SQL Server. */
@@ -915,20 +918,19 @@ declare namespace gapi.client {
915
918
  pscConfig?:
916
919
  PscConfig;
917
920
  /**
918
- * 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
919
- * 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
920
- * SSL/TLS without enforcing the requirement for valid client certificates, use the `ssl_mode` flag instead of the legacy `require_ssl` flag.
921
- * LINT.ThenChange(//depot/google3/java/com/google/storage/speckle/boss/admin/actions/InstanceUpdateAction.java:update_api_temp_fix)
921
+ * 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
922
+ * 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
923
+ * valid client certificates, then use the `ssl_mode` flag instead of the legacy `require_ssl` flag.
922
924
  */
923
925
  requireSsl?:
924
926
  boolean;
925
927
  /**
926
- * 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
927
- * 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
928
- * following value pairs are valid: ssl_mode=ALLOW_UNENCRYPTED_AND_ENCRYPTED, require_ssl=false; ssl_mode=ENCRYPTED_ONLY, require_ssl=false;
929
- * 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
930
- * `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
931
- * connections are allowed". The database will respect `ssl_mode` in this case and only accept SSL connections.
928
+ * 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.
929
+ * 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
930
+ * 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
931
+ * `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,
932
+ * 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
933
+ * database respects `ssl_mode` in this case and only accepts SSL connections.
932
934
  */
933
935
  sslMode?:
934
936
  string;
@@ -1170,9 +1172,6 @@ declare namespace gapi.client {
1170
1172
  /** The complexity of the password. */
1171
1173
  complexity?:
1172
1174
  string;
1173
- /** Disallow credentials that have been previously compromised by a public data breach. */
1174
- disallowCompromisedCredentials?:
1175
- boolean;
1176
1175
  /** Disallow username as a part of the password. */
1177
1176
  disallowUsernameSubstring?:
1178
1177
  boolean;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@maxim_mazurok/gapi.client.sqladmin-v1",
3
- "version": "0.0.20231011",
3
+ "version": "0.0.20231017",
4
4
  "description": "TypeScript typings for Cloud SQL Admin API v1",
5
5
  "license": "MIT",
6
6
  "author": {
package/tests.ts CHANGED
@@ -3,7 +3,7 @@
3
3
  // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
4
4
  // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
5
5
 
6
- // Revision: 20231011
6
+ // Revision: 20231017
7
7
 
8
8
  gapi.load('client', async () => {
9
9
  /** now we can use gapi.client */
@@ -533,7 +533,6 @@ gapi.load('client', async () => {
533
533
  },
534
534
  passwordValidationPolicy: {
535
535
  complexity: "Test string",
536
- disallowCompromisedCredentials: true,
537
536
  disallowUsernameSubstring: true,
538
537
  enablePasswordPolicy: true,
539
538
  minLength: 42,
@@ -782,7 +781,6 @@ gapi.load('client', async () => {
782
781
  },
783
782
  passwordValidationPolicy: {
784
783
  complexity: "Test string",
785
- disallowCompromisedCredentials: true,
786
784
  disallowUsernameSubstring: true,
787
785
  enablePasswordPolicy: true,
788
786
  minLength: 42,
@@ -1090,7 +1088,6 @@ gapi.load('client', async () => {
1090
1088
  },
1091
1089
  passwordValidationPolicy: {
1092
1090
  complexity: "Test string",
1093
- disallowCompromisedCredentials: true,
1094
1091
  disallowUsernameSubstring: true,
1095
1092
  enablePasswordPolicy: true,
1096
1093
  minLength: 42,