Discovery API monitoring and real-time diff analysis for AlloyDB.
Never miss an API update, method deprecation, or breaking change in AlloyDB.
AlloyDB's autoscaling policies for read pools can now leverage connection count as a scaling metric. This allows for more granular control, enabling dynamic adjustments based on the number of active database connections.
AlloyDB v1beta now introduces a new autoscaling policy type based on connection count. You can configure your autoscaler to scale instances based on a target number of connections.
AlloyDB introduces a new `connectionsCount` policy for autoscaling, allowing you to scale instances based on the target number of active connections. This provides finer-grained control over resource allocation.
AlloyDB v1beta now exposes cluster Certificate Authority (CA) details and instance network information as read-only properties. Developers should note that several new fields, including CA certificates and instance network details, are now explicitly output-only, which is a breaking change if you were attempting to set them.
AlloyDB now provides crucial CA certificate information for secure PostgreSQL connections and public DNS names for instances. A new `publicDnsEnabled` option allows configuring public DNS. Be aware of breaking changes as `rootCaCert`, `certificateAuthorityInfo`, `networkInfo`, and `publicDnsName` are now read-only.
The recently introduced `edition` field on AlloyDB `Cluster` and `Backup` schemas is now deprecated. Developers should transition to using the new `expressConfig` property on `Backup` for Express cluster details, which is output-only and considered a breaking change if you anticipated setting it.
The `edition` field on both `Backup` and `Cluster` resources is now deprecated, with a recommendation to use the `ExpressConfig` property instead. Additionally, the `expressConfig` property on `Backup` has been made read-only, which is a breaking change if you were previously setting it.
AlloyDB now supports autoscaling for read pools, allowing you to dynamically adjust the number of read replica nodes based on CPU utilization or predefined schedules. This significantly simplifies managing read capacity and optimizing costs.
AlloyDB v1beta now supports Express clusters via a new `expressConfig` property on the `Cluster` schema. Developers should note significant breaking changes: several observability and query insights properties on `Instance` and related schemas are now read-only.
AlloyDB v1alpha now supports creating Express clusters. Be aware of breaking changes: several observability and query insights fields on `Instance` are now read-only, becoming output-only information.
AlloyDB instances now expose `observabilityInstanceInfo` and `queryInsightsInfo` as output-only fields. Any existing code attempting to modify these properties will now encounter errors, as they are strictly immutable. Update your integrations to treat these as informational.
The `trackActiveQueryPlan` property within AlloyDB's `ObservabilityInstanceConfig` schema has been deprecated. Developers should plan to migrate away from using this feature.
The `trackActiveQueryPlan` field within the `ObservabilityInstanceConfig` schema has been marked as deprecated. Developers should update their configurations to avoid using this field.
AlloyDB now supports new `userType` enum values for IAM group-based authentication, enabling more flexible and granular control over database access for groups, users, and service accounts.
AlloyDB v1beta introduces support for PostgreSQL 19 and a new Edition classification for clusters, including a Developer edition. Note that the edition field on Backups is now read-only.
AlloyDB v1alpha introduces support for Postgres 19 and a new edition classification for clusters, while making the edition field read-only on backups.
