Bug fixes

• Opening the Cloud SQL console no longer produces false activity in Guardrails. GCP logs the console's free-trial eligibility check as an instance-create audit event, and the GCP > SQL > Instance router treated it as a real creation — briefly recording a phantom SQL Instance named after the project, which the CMDB control then deleted, leaving a misleading create/delete pair attributed to whoever opened the console. The router now ignores these checks, and any other event that does not target a specific SQL instance.
• Cloned Cloud SQL instances now appear in the CMDB in real time. The clone audit event identifies the source instance, so the router never recorded the new instance; it now reads the destination instance name from the clone request.

What's new?

• The Usage controls and their Usage and Usage > Limit policies have been retired from the GCP SQL Backup, Database, and Instance resource types. The Approved > Usage policies are unaffected and remain available.

Control Types

Removed

• GCP > SQL > Backup > Usage
• GCP > SQL > Database > Usage
• GCP > SQL > Instance > Usage

Policy Types

Removed

• GCP > SQL > Backup > Usage
• GCP > SQL > Backup > Usage > Limit
• GCP > SQL > Database > Usage
• GCP > SQL > Database > Usage > Limit
• GCP > SQL > Instance > Usage
• GCP > SQL > Instance > Usage > Limit