Workload Capture/Replay Request Schemas Renamed
The request body schemas for Cloud SQL Admin API's workload capture and replay methods have been renamed, requiring updates to client code.
Discovery API monitoring and real-time diff analysis for Cloud SQL.
Never miss an API update, method deprecation, or breaking change in Cloud SQL.
The request body schemas for Cloud SQL Admin API's workload capture and replay methods have been renamed, requiring updates to client code.
The request body schemas for Cloud SQL's Workload Capture methods (start, startReplay, stop, stopReplay) have been renamed. This is a breaking change requiring updates to client code.
The `workloadCaptures.stopReplay` method has undergone a breaking change, removing the `workloadId` parameter from its URI path and altering the `StopWorkloadReplayContext` schema. This is a significant adjustment to the recently introduced workload replay functionality.
The `workloadCaptures.stopReplay` method has undergone a breaking refactor. The `workloadId` path parameter is removed, and the `StopWorkloadReplayContext` schema no longer includes `replayInstance` or `workloadId` properties. This requires immediate code updates.
Cloud SQL introduces new controls for major version upgrades and Database Center integration. The `WorkloadCapture` schema also sees updates, including a new `TERMINATED` state and a breaking change where `backupId` is now read-only.
The `backupId` field in `WorkloadCapture` is now read-only, requiring updates for any code attempting to set it. Additionally, `DatabaseInstance` gains new controls for Database Center integration and major version upgrade prechecks.
Cloud SQL adds a new suite of methods to capture production database traffic and replay it on test instances for performance and upgrade validation.
The Cloud SQL Admin API introduces strict validation and immutability rules for Workload Capture schemas, alongside new methods to list, start, stop, and replay database workloads.