@googleapis/alloydb 10.0.0 → 11.1.0

package/v1.ts

@@ -436,6 +436,35 @@ export namespace alloydb_v1 {
      */
     updateTime?: string | null;
   }
+  /**
+   * Upgrade details of a cluster. This cluster can be primary or secondary.
+   */
+  export interface Schema$ClusterUpgradeDetails {
+    /**
+     * Cluster type which can either be primary or secondary.
+     */
+    clusterType?: string | null;
+    /**
+     * Database version of the cluster after the upgrade operation. This will be the target version if the upgrade was successful otherwise it remains the same as that before the upgrade operation.
+     */
+    databaseVersion?: string | null;
+    /**
+     * Upgrade details of the instances directly associated with this cluster.
+     */
+    instanceUpgradeDetails?: Schema$InstanceUpgradeDetails[];
+    /**
+     * Normalized name of the cluster
+     */
+    name?: string | null;
+    /**
+     * Array containing stage info associated with this cluster.
+     */
+    stageInfo?: Schema$StageInfo[];
+    /**
+     * Upgrade status of the cluster.
+     */
+    upgradeStatus?: string | null;
+  }
   /**
    * ConnectionInfo singleton resource. https://google.aip.dev/156
    */
@@ -745,6 +774,23 @@ export namespace alloydb_v1 {
      */
     enablePublicIp?: boolean | null;
   }
+  /**
+   * Details regarding the upgrade of instaces associated with a cluster.
+   */
+  export interface Schema$InstanceUpgradeDetails {
+    /**
+     * Instance type.
+     */
+    instanceType?: string | null;
+    /**
+     * Normalized name of the instance.
+     */
+    name?: string | null;
+    /**
+     * Upgrade status of the instance.
+     */
+    upgradeStatus?: string | null;
+  }
   /**
    * Restrictions on INTEGER type values.
    */
@@ -1106,6 +1152,10 @@ export namespace alloydb_v1 {
     nodeCount?: number | null;
   }
   export interface Schema$RestartInstanceRequest {
+    /**
+     * Optional. Full name of the nodes as obtained from INSTANCE_VIEW_FULL to restart upon. Only applicable for read instances.
+     */
+    nodeIds?: string[] | null;
     /**
      * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
      */
@@ -1166,6 +1216,23 @@ export namespace alloydb_v1 {
      */
     sslMode?: string | null;
   }
+  /**
+   * Stage information for different stages in the upgrade process.
+   */
+  export interface Schema$StageInfo {
+    /**
+     * logs_url is the URL for the logs associated with a stage if that stage has logs. Right now, only three stages have logs: ALLOYDB_PRECHECK, PG_UPGRADE_CHECK, PRIMARY_INSTANCE_UPGRADE.
+     */
+    logsUrl?: string | null;
+    /**
+     * The stage.
+     */
+    stage?: string | null;
+    /**
+     * Status of the stage.
+     */
+    status?: string | null;
+  }
   /**
    * The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors).
    */
@@ -1187,6 +1254,10 @@ export namespace alloydb_v1 {
    * Configuration for availability of database instance
    */
   export interface Schema$StorageDatabasecenterPartnerapiV1mainAvailabilityConfiguration {
+    /**
+     * Checks for existence of (multi-cluster) routing configuration that allows automatic failover to a different zone/region in case of an outage. Applicable to Bigtable resources.
+     */
+    automaticFailoverRoutingConfigured?: boolean | null;
     /**
      * Availability type. Potential values: * `ZONAL`: The instance serves data from only one zone. Outages in that zone affect data accessibility. * `REGIONAL`: The instance can serve data from more than one zone in a region (it is highly available).
      */
@@ -1250,29 +1321,13 @@ export namespace alloydb_v1 {
     version?: string | null;
   }
   /**
-   * Any custom metadata associated with the resource. i.e. A spanner instance can have multiple databases with its own unique metadata. Information for these individual databases can be captured in custom metadata data
+   * Any custom metadata associated with the resource. e.g. A spanner instance can have multiple databases with its own unique metadata. Information for these individual databases can be captured in custom metadata data
    */
   export interface Schema$StorageDatabasecenterPartnerapiV1mainCustomMetadataData {
-    databaseMetadata?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseMetadata[];
-  }
-  /**
-   * Metadata for individual databases created in an instance. i.e. spanner instance can have multiple databases with unique configuration settings.
-   */
-  export interface Schema$StorageDatabasecenterPartnerapiV1mainDatabaseMetadata {
     /**
-     * Backup configuration for this database
-     */
-    backupConfiguration?: Schema$StorageDatabasecenterPartnerapiV1mainBackupConfiguration;
-    /**
-     * Information about the last backup attempt for this database
-     */
-    backupRun?: Schema$StorageDatabasecenterPartnerapiV1mainBackupRun;
-    product?: Schema$StorageDatabasecenterProtoCommonProduct;
-    resourceId?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceId;
-    /**
-     * Required. Database name. Resource name to follow CAIS resource_name format as noted here go/condor-common-datamodel
+     * Metadata for individual internal resources in an instance. e.g. spanner instance can have multiple databases with unique configuration.
      */
-    resourceName?: string | null;
+    internalResourceMetadata?: Schema$StorageDatabasecenterPartnerapiV1mainInternalResourceMetadata[];
   }
   /**
    * DatabaseResourceFeed is the top level proto to be used to ingest different database resource level events into Condor platform.
@@ -1286,9 +1341,6 @@ export namespace alloydb_v1 {
      * Required. Type feed to be ingested into condor
      */
     feedType?: string | null;
-    /**
-     * More feed data would be added in subsequent CLs
-     */
     observabilityMetricData?: Schema$StorageDatabasecenterPartnerapiV1mainObservabilityMetricData;
     recommendationSignalData?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceRecommendationSignalData;
     resourceHealthSignalData?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceHealthSignalData;
@@ -1346,6 +1398,10 @@ export namespace alloydb_v1 {
      * Required. Unique identifier for the signal. This is an unique id which would be mainatined by partner to identify a signal.
      */
     signalId?: string | null;
+    /**
+     * The severity of the signal, such as if it's a HIGH or LOW severity.
+     */
+    signalSeverity?: string | null;
     /**
      * Required. Type of signal, for example, `AVAILABLE_IN_MULTIPLE_ZONES`, `LOGGING_MOST_ERRORS`, etc.
      */
@@ -1365,7 +1421,7 @@ export namespace alloydb_v1 {
      */
     providerDescription?: string | null;
     /**
-     * Required. The type of resource this ID is identifying. Ex redis.googleapis.com/Instance, redis.googleapis.com/Cluster, alloydb.googleapis.com/Cluster, alloydb.googleapis.com/Instance, spanner.googleapis.com/Instance REQUIRED Please refer go/condor-common-datamodel
+     * Required. The type of resource this ID is identifying. Ex redis.googleapis.com/Instance, redis.googleapis.com/Cluster, alloydb.googleapis.com/Cluster, alloydb.googleapis.com/Instance, spanner.googleapis.com/Instance, spanner.googleapis.com/Database, firestore.googleapis.com/Database, sqladmin.googleapis.com/Instance, bigtableadmin.googleapis.com/Cluster, bigtableadmin.googleapis.com/Instance REQUIRED Please refer go/condor-common-datamodel
      */
     resourceType?: string | null;
     /**
@@ -1500,6 +1556,25 @@ export namespace alloydb_v1 {
      */
     type?: string | null;
   }
+  /**
+   * Metadata for individual internal resources in an instance. e.g. spanner instance can have multiple databases with unique configuration settings. Similarly bigtable can have multiple clusters within same bigtable instance.
+   */
+  export interface Schema$StorageDatabasecenterPartnerapiV1mainInternalResourceMetadata {
+    /**
+     * Backup configuration for this database
+     */
+    backupConfiguration?: Schema$StorageDatabasecenterPartnerapiV1mainBackupConfiguration;
+    /**
+     * Information about the last backup attempt for this database
+     */
+    backupRun?: Schema$StorageDatabasecenterPartnerapiV1mainBackupRun;
+    product?: Schema$StorageDatabasecenterProtoCommonProduct;
+    resourceId?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceId;
+    /**
+     * Required. internal resource name for spanner this will be database name e.g."spanner.googleapis.com/projects/123/abc/instances/inst1/databases/db1"
+     */
+    resourceName?: string | null;
+  }
   /**
    * MachineConfiguration describes the configuration of a machine specific to Database Resource.
    */
@@ -1674,6 +1749,10 @@ export namespace alloydb_v1 {
      * End time of the trial cluster.
      */
     endTime?: string | null;
+    /**
+     * grace end time of the cluster.
+     */
+    graceEndTime?: string | null;
     /**
      * start time of the trial cluster.
      */
@@ -1683,6 +1762,23 @@ export namespace alloydb_v1 {
      */
     upgradeTime?: string | null;
   }
+  /**
+   * UpgradeClusterResponse contains the response for upgrade cluster operation.
+   */
+  export interface Schema$UpgradeClusterResponse {
+    /**
+     * Array of upgrade details for the current cluster and all the secondary clusters associated with this cluster.
+     */
+    clusterUpgradeDetails?: Schema$ClusterUpgradeDetails[];
+    /**
+     * A user friendly message summarising the upgrade operation details and the next steps for the user if there is any.
+     */
+    message?: string | null;
+    /**
+     * Status of upgrade operation.
+     */
+    status?: string | null;
+  }
   /**
    * Message describing User object.
    */
@@ -1691,6 +1787,10 @@ export namespace alloydb_v1 {
      * Optional. List of database roles this user has. The database role strings are subject to the PostgreSQL naming conventions.
      */
     databaseRoles?: string[] | null;
+    /**
+     * Input only. If the user already exists and it has additional roles, keep them granted.
+     */
+    keepExtraRoles?: boolean | null;
     /**
      * Output only. Name of the resource in the form of projects/{project\}/locations/{location\}/cluster/{cluster\}/users/{user\}.
      */

package/v1alpha.ts

@@ -1378,6 +1378,10 @@ export namespace alloydb_v1alpha {
    * Configuration for availability of database instance
    */
   export interface Schema$StorageDatabasecenterPartnerapiV1mainAvailabilityConfiguration {
+    /**
+     * Checks for existence of (multi-cluster) routing configuration that allows automatic failover to a different zone/region in case of an outage. Applicable to Bigtable resources.
+     */
+    automaticFailoverRoutingConfigured?: boolean | null;
     /**
      * Availability type. Potential values: * `ZONAL`: The instance serves data from only one zone. Outages in that zone affect data accessibility. * `REGIONAL`: The instance can serve data from more than one zone in a region (it is highly available).
      */
@@ -1937,6 +1941,10 @@ export namespace alloydb_v1alpha {
      * Optional. List of database roles this user has. The database role strings are subject to the PostgreSQL naming conventions.
      */
     databaseRoles?: string[] | null;
+    /**
+     * Input only. If the user already exists and it has additional roles, keep them granted.
+     */
+    keepExtraRoles?: boolean | null;
     /**
      * Output only. Name of the resource in the form of projects/{project\}/locations/{location\}/cluster/{cluster\}/users/{user\}.
      */

package/v1beta.ts

@@ -302,6 +302,23 @@ export namespace alloydb_v1beta {
      */
     exclusiveAction?: string | null;
   }
+  /**
+   * The source CloudSQL backup resource.
+   */
+  export interface Schema$CloudSQLBackupRunSource {
+    /**
+     * Required. The CloudSQL backup run ID.
+     */
+    backupRunId?: string | null;
+    /**
+     * Required. The CloudSQL instance ID.
+     */
+    instanceId?: string | null;
+    /**
+     * The project ID of the source CloudSQL instance. This should be the same as the AlloyDB cluster's project.
+     */
+    project?: string | null;
+  }
   /**
    * A cluster is a collection of regional AlloyDB resources. It can include a primary instance and one or more read pool instances. All cluster resources share a storage layer, which scales as needed.
    */
@@ -318,6 +335,10 @@ export namespace alloydb_v1beta {
      * Output only. Cluster created from backup.
      */
     backupSource?: Schema$BackupSource;
+    /**
+     * Output only. Cluster created from CloudSQL snapshot.
+     */
+    cloudsqlBackupRunSource?: Schema$CloudSQLBackupRunSource;
     /**
      * Output only. The type of the cluster. This is an output-only field and it's populated at the Cluster creation time or the Cluster promotion time. The cluster type is determined by which RPC was used to create the cluster (i.e. `CreateCluster` vs. `CreateSecondaryCluster`
      */
@@ -436,6 +457,35 @@ export namespace alloydb_v1beta {
      */
     updateTime?: string | null;
   }
+  /**
+   * Upgrade details of a cluster. This cluster can be primary or secondary.
+   */
+  export interface Schema$ClusterUpgradeDetails {
+    /**
+     * Cluster type which can either be primary or secondary.
+     */
+    clusterType?: string | null;
+    /**
+     * Database version of the cluster after the upgrade operation. This will be the target version if the upgrade was successful otherwise it remains the same as that before the upgrade operation.
+     */
+    databaseVersion?: string | null;
+    /**
+     * Upgrade details of the instances directly associated with this cluster.
+     */
+    instanceUpgradeDetails?: Schema$InstanceUpgradeDetails[];
+    /**
+     * Normalized name of the cluster
+     */
+    name?: string | null;
+    /**
+     * Array containing stage info associated with this cluster.
+     */
+    stageInfo?: Schema$StageInfo[];
+    /**
+     * Upgrade status of the cluster.
+     */
+    upgradeStatus?: string | null;
+  }
   /**
    * ConnectionInfo singleton resource. https://google.aip.dev/156
    */
@@ -791,6 +841,23 @@ export namespace alloydb_v1beta {
      */
     enablePublicIp?: boolean | null;
   }
+  /**
+   * Details regarding the upgrade of instaces associated with a cluster.
+   */
+  export interface Schema$InstanceUpgradeDetails {
+    /**
+     * Instance type.
+     */
+    instanceType?: string | null;
+    /**
+     * Normalized name of the instance.
+     */
+    name?: string | null;
+    /**
+     * Upgrade status of the instance.
+     */
+    upgradeStatus?: string | null;
+  }
   /**
    * Restrictions on INTEGER type values.
    */
@@ -1017,6 +1084,10 @@ export namespace alloydb_v1beta {
      * Track actively running queries on the instance. If not set, this flag is "off" by default.
      */
     trackActiveQueries?: boolean | null;
+    /**
+     * Track client address for an instance. If not set, default value is "off".
+     */
+    trackClientAddress?: boolean | null;
     /**
      * Track wait events during query execution for an instance. This flag is turned "on" by default but tracking is enabled only after observability enabled flag is also turned on.
      */
@@ -1189,6 +1260,10 @@ export namespace alloydb_v1beta {
     nodeCount?: number | null;
   }
   export interface Schema$RestartInstanceRequest {
+    /**
+     * Optional. Full name of the nodes as obtained from INSTANCE_VIEW_FULL to restart upon. Only applicable for read instances.
+     */
+    nodeIds?: string[] | null;
     /**
      * Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes after the first request. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000).
      */
@@ -1249,6 +1324,23 @@ export namespace alloydb_v1beta {
      */
     sslMode?: string | null;
   }
+  /**
+   * Stage information for different stages in the upgrade process.
+   */
+  export interface Schema$StageInfo {
+    /**
+     * logs_url is the URL for the logs associated with a stage if that stage has logs. Right now, only three stages have logs: ALLOYDB_PRECHECK, PG_UPGRADE_CHECK, PRIMARY_INSTANCE_UPGRADE.
+     */
+    logsUrl?: string | null;
+    /**
+     * The stage.
+     */
+    stage?: string | null;
+    /**
+     * Status of the stage.
+     */
+    status?: string | null;
+  }
   /**
    * The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors).
    */
@@ -1333,29 +1425,13 @@ export namespace alloydb_v1beta {
     version?: string | null;
   }
   /**
-   * Any custom metadata associated with the resource. i.e. A spanner instance can have multiple databases with its own unique metadata. Information for these individual databases can be captured in custom metadata data
+   * Any custom metadata associated with the resource. e.g. A spanner instance can have multiple databases with its own unique metadata. Information for these individual databases can be captured in custom metadata data
    */
   export interface Schema$StorageDatabasecenterPartnerapiV1mainCustomMetadataData {
-    databaseMetadata?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseMetadata[];
-  }
-  /**
-   * Metadata for individual databases created in an instance. i.e. spanner instance can have multiple databases with unique configuration settings.
-   */
-  export interface Schema$StorageDatabasecenterPartnerapiV1mainDatabaseMetadata {
     /**
-     * Backup configuration for this database
+     * Metadata for individual internal resources in an instance. e.g. spanner instance can have multiple databases with unique configuration.
      */
-    backupConfiguration?: Schema$StorageDatabasecenterPartnerapiV1mainBackupConfiguration;
-    /**
-     * Information about the last backup attempt for this database
-     */
-    backupRun?: Schema$StorageDatabasecenterPartnerapiV1mainBackupRun;
-    product?: Schema$StorageDatabasecenterProtoCommonProduct;
-    resourceId?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceId;
-    /**
-     * Required. Database name. Resource name to follow CAIS resource_name format as noted here go/condor-common-datamodel
-     */
-    resourceName?: string | null;
+    internalResourceMetadata?: Schema$StorageDatabasecenterPartnerapiV1mainInternalResourceMetadata[];
   }
   /**
    * DatabaseResourceFeed is the top level proto to be used to ingest different database resource level events into Condor platform.
@@ -1369,9 +1445,6 @@ export namespace alloydb_v1beta {
      * Required. Type feed to be ingested into condor
      */
     feedType?: string | null;
-    /**
-     * More feed data would be added in subsequent CLs
-     */
     observabilityMetricData?: Schema$StorageDatabasecenterPartnerapiV1mainObservabilityMetricData;
     recommendationSignalData?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceRecommendationSignalData;
     resourceHealthSignalData?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceHealthSignalData;
@@ -1429,6 +1502,10 @@ export namespace alloydb_v1beta {
      * Required. Unique identifier for the signal. This is an unique id which would be mainatined by partner to identify a signal.
      */
     signalId?: string | null;
+    /**
+     * The severity of the signal, such as if it's a HIGH or LOW severity.
+     */
+    signalSeverity?: string | null;
     /**
      * Required. Type of signal, for example, `AVAILABLE_IN_MULTIPLE_ZONES`, `LOGGING_MOST_ERRORS`, etc.
      */
@@ -1448,7 +1525,7 @@ export namespace alloydb_v1beta {
      */
     providerDescription?: string | null;
     /**
-     * Required. The type of resource this ID is identifying. Ex redis.googleapis.com/Instance, redis.googleapis.com/Cluster, alloydb.googleapis.com/Cluster, alloydb.googleapis.com/Instance, spanner.googleapis.com/Instance REQUIRED Please refer go/condor-common-datamodel
+     * Required. The type of resource this ID is identifying. Ex redis.googleapis.com/Instance, redis.googleapis.com/Cluster, alloydb.googleapis.com/Cluster, alloydb.googleapis.com/Instance, spanner.googleapis.com/Instance, spanner.googleapis.com/Database, firestore.googleapis.com/Database, sqladmin.googleapis.com/Instance, bigtableadmin.googleapis.com/Cluster, bigtableadmin.googleapis.com/Instance REQUIRED Please refer go/condor-common-datamodel
      */
     resourceType?: string | null;
     /**
@@ -1583,6 +1660,25 @@ export namespace alloydb_v1beta {
      */
     type?: string | null;
   }
+  /**
+   * Metadata for individual internal resources in an instance. e.g. spanner instance can have multiple databases with unique configuration settings. Similarly bigtable can have multiple clusters within same bigtable instance.
+   */
+  export interface Schema$StorageDatabasecenterPartnerapiV1mainInternalResourceMetadata {
+    /**
+     * Backup configuration for this database
+     */
+    backupConfiguration?: Schema$StorageDatabasecenterPartnerapiV1mainBackupConfiguration;
+    /**
+     * Information about the last backup attempt for this database
+     */
+    backupRun?: Schema$StorageDatabasecenterPartnerapiV1mainBackupRun;
+    product?: Schema$StorageDatabasecenterProtoCommonProduct;
+    resourceId?: Schema$StorageDatabasecenterPartnerapiV1mainDatabaseResourceId;
+    /**
+     * Required. internal resource name for spanner this will be database name e.g."spanner.googleapis.com/projects/123/abc/instances/inst1/databases/db1"
+     */
+    resourceName?: string | null;
+  }
   /**
    * MachineConfiguration describes the configuration of a machine specific to Database Resource.
    */
@@ -1757,6 +1853,10 @@ export namespace alloydb_v1beta {
      * End time of the trial cluster.
      */
     endTime?: string | null;
+    /**
+     * grace end time of the cluster.
+     */
+    graceEndTime?: string | null;
     /**
      * start time of the trial cluster.
      */
@@ -1775,6 +1875,23 @@ export namespace alloydb_v1beta {
      */
     mode?: string | null;
   }
+  /**
+   * UpgradeClusterResponse contains the response for upgrade cluster operation.
+   */
+  export interface Schema$UpgradeClusterResponse {
+    /**
+     * Array of upgrade details for the current cluster and all the secondary clusters associated with this cluster.
+     */
+    clusterUpgradeDetails?: Schema$ClusterUpgradeDetails[];
+    /**
+     * A user friendly message summarising the upgrade operation details and the next steps for the user if there is any.
+     */
+    message?: string | null;
+    /**
+     * Status of upgrade operation.
+     */
+    status?: string | null;
+  }
   /**
    * Message describing User object.
    */