Product logo
DocsBlogPricing

@turbot/gcp-sql

The gcp-sql mod contains resource, control and policy definitions for GCP SQL service.

Version
5.8.1
Released On
Apr 04, 2024
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.8.1 (2024-04-04)

Bug fixes

  • SQL Instances were sometimes not updated/cleaned up correctly via real-time events in Guardrails. This is now fixed.

5.8.0 (2024-02-01)

What's new?

  • We've updated the runtime of the lambda functions to Node 18. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.

5.7.1 (2023-06-28)

Bug fixes

  • We've updated the runtime of the lambda functions to Node 18. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.

5.7.0 (2023-06-12)

What's new?

  • Resource's metadata will now also include createdBy details in Turbot CMDB.

5.6.2 (2023-06-08)

Bug fixes

  • Guardrails would sometimes incorrectly upsert Instances with project name as their instance name in Guardrails CMDB, while processing cloudsql.instances.create real-time events. This is fixed and the instance create events will now be processed correctly in Turbot.

5.6.1 (2022-10-28)

Bug fixes

  • We've updated the runtime of the lambda functions to node 16. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.

5.6.0 (2022-02-17)

What's new?

  • Users can now create their own custom checks against resource attributes in the Approved control using the Approved > Custom policy. These custom checks would be a part of the evaluation of the Approved control. Custom messages can also be added which are then displayed in the control details table. See Custom Checks for more information.

Bug fixes

  • We've improved the process of deleting resources from Guardrails if their CMDB policy was set to Enforce: Disabled. The CMDB controls will now not look to resolve credentials via Guardrails' IAM role while deleting resources from Turbot. This will allow the CMDB controls to process resource deletions from Guardrails more reliably than before.

Policy Types

  • GCP > SQL > Backup > Approved > Custom
  • GCP > SQL > Database > Approved > Custom
  • GCP > SQL > Instance > Approved > Custom

5.5.0 (2021-08-02)

What's new?

  • We've improved the details tables in the Tags controls to be more helpful, especially when a resource's tags are not set correctly as expected. Previously, to understand why the Tags controls were in an Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.

Bug fixes

  • We’ve made a few improvements in the GraphQL queries for various controls, policies, and actions. You won’t notice any difference, but things should run lighter and quicker than before.

5.4.0 (2021-02-25)

What's new?

  • We've improved the state reasons and details tables in various Approved and Active controls to be more helpful, especially when a resource is unapproved or inactive. Previously, to understand why one of these controls is in Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.

5.3.3 (2021-02-01)

Bug fixes

  • SQL server instances created in the us-central1 and asia-east1 regions were not upserted in CMDB through real-time events. This is now fixed.

5.3.2 (2021-01-21)

Bug fixes

  • Controls run faster now when in the tbd and skipped states thanks to the new Turbot Precheck feature (not to be confused with TSA PreCheck). With Turbot Precheck, controls avoid running GraphQL input queries when in tbd and skipped, resulting in faster and lighter control runs.

5.3.1 (2020-12-03)

Bug fixes

  • We've updated the GCP > * > Set API Enabled actions to use the latest API calls when checking the state of the service in the GCP project. There's no noticeable difference, but things should run smoother now.

5.3.0 (2020-11-02)

What's new?

  • We've made improvements to how Active controls interact with CMDB policies and controls for more reliable active checks. Now, if a resource's CMDB policy is set to Skip, its Active control will move to invalid to prevent the Active control from making a decision based on outdated information. Also, Active controls will now wait until the resource's CMDB control has run at least once to ensure the required data is available.

Bug fixes

  • We've updated the Discovery controls for resources to now move to skipped instead of invalid if the service API is disabled in the project and the GCP > {service} > API Enabled policy is checking if the API is disabled. This will reduce the amount of noisy controls that cannot be easily resolved without making changes to the service API.

5.2.0 (2020-08-28)

What's new?

  • Discovery controls now have their own control category, CMDB > Discovery, to allow for easier filtering separately from other CMDB controls.

5.1.9 (2020-08-10)

Bug fixes

  • When attempting to list, update, or delete a database, if its instance's activation policy was set to SQL_ACTIVATION_POLICY_UNSPECIFIED or NEVER, various database controls would move into error state as the database APIs are not available for that instance. These errors have been fixed and we now properly check the instance's activation policy before making any database API calls.

5.1.8 (2020-07-24)

Bug fixes

  • Active controls for all resources were not calling the delete action properly, which meant inactive resources were not being deleted when the policy was set to enforce deletions. This has been fixed and inactive resources will now be cleaned up again.

5.1.7 (2020-06-19)

Bug fixes

  • Although the data validation errors, which appear in various CMDB and Discovery controls, are not blockers, they look ugly in the UI and should be cleaned up. These errors have now been fixed.

5.1.6 (2020-06-03)

What's new?

  • All resource Router actions now run even if Guardrails is outside of its allowed change window. This allows Guardrails to maintain an up-to-date CMDB by handling resource updates at all times. Note that this only affects Guardrails' ability to process resources changes that were made in the cloud provider - enforcement actions are still disabled outside of the change window.

5.1.5 (2020-05-20)

Bug fixes

  • Only instances using database engines MySQL 5.6 and 5.7 support binary log configuration, so the GCP > SQL > Instance > Binary Log control will now skip checking this setting for PostgreSQL and SQL Server instances.

5.1.4 (2020-05-14)

Bug fixes

  • Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.

5.1.3 (2020-05-06)

Bug fixes

  • While importing a GCP project, sometimes resources' Discovery controls would get stuck in an Invalid state due to incorrectly configured dependencies. This has been fixed and project imports should be smooth again.
  • The GCP > SQL > Instance > Labels control will now wait for the instance to be in the RUNNABLE state before attempting to apply any labels.
  • If the GCP > SQL > Database > Discovery control ran while the database's instance was in any state other than RUNNABLE, it would move to Error state. Now the control will wait for the instance to be in the RUNNABLE state before running.

Control Types

Renamed

  • GCP > SQL > Instance > Backup Configuration setting to GCP > SQL > Instance > Backup Configuration
  • GCP > SQL > Instance > Binary Log setting to GCP > SQL > Instance > Binary Log

Policy Types

Renamed

  • GCP > SQL > Instance > Backup Configuration setting to GCP > SQL > Instance > Backup Configuration
  • GCP > SQL > Instance > Binary Log setting to GCP > SQL > Instance > Binary Log

5.1.2 (2020-04-20)

Bug fixes

  • The SQL instance Binary Log Enabled control was stuck in an error state due to a bad GraphQL input. This has been fixed.
  • The SQL instance Backup Configuration Enabled control was stuck in an error state due to a bad GraphQL input. This has been fixed.

Policy Types

Renamed

  • GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > SQL to GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-sql

5.1.1 (2020-04-14)

Bug fixes

  • All controls that used the Cloud SQL API were in error due to them using the deprecated connection service. These are all now connecting to the correct service.

5.1.0 (2020-04-13)

What's new?

  • Services can now be enabled as Metadata only, restricting users to only use metadata level permissions.

Bug fixes

  • Many calculations for Permissions > Compiled > Service Permissions were in error due to a missing library. This is now fixed.

5.0.0 (2020-04-08)

Resource Types

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

Control Types

  • GCP > SQL > API Enabled
  • GCP > SQL > Backup > Active
  • GCP > SQL > Backup > Approved
  • GCP > SQL > Backup > CMDB
  • GCP > SQL > Backup > Discovery
  • GCP > SQL > Backup > Usage
  • GCP > SQL > CMDB
  • GCP > SQL > Database > Active
  • GCP > SQL > Database > Approved
  • GCP > SQL > Database > CMDB
  • GCP > SQL > Database > Discovery
  • GCP > SQL > Database > Usage
  • GCP > SQL > Discovery
  • GCP > SQL > Instance > Active
  • GCP > SQL > Instance > Approved
  • GCP > SQL > Instance > Backup Configuration setting
  • GCP > SQL > Instance > Binary Log setting
  • GCP > SQL > Instance > CMDB
  • GCP > SQL > Instance > Data Protection
  • GCP > SQL > Instance > Discovery
  • GCP > SQL > Instance > Labels
  • GCP > SQL > Instance > Usage

Policy Types

  • GCP > SQL > API Enabled
  • GCP > SQL > Approved Regions [Default]
  • GCP > SQL > Backup > Active
  • GCP > SQL > Backup > Active > Age
  • GCP > SQL > Backup > Active > Last Modified
  • GCP > SQL > Backup > Approved
  • GCP > SQL > Backup > Approved > Regions
  • GCP > SQL > Backup > Approved > Usage
  • GCP > SQL > Backup > CMDB
  • GCP > SQL > Backup > Regions
  • GCP > SQL > Backup > Usage
  • GCP > SQL > Backup > Usage > Limit
  • GCP > SQL > CMDB
  • GCP > SQL > Database > Active
  • GCP > SQL > Database > Active > Age
  • GCP > SQL > Database > Active > Last Modified
  • GCP > SQL > Database > Approved
  • GCP > SQL > Database > Approved > Regions
  • GCP > SQL > Database > Approved > Usage
  • GCP > SQL > Database > CMDB
  • GCP > SQL > Database > Regions
  • GCP > SQL > Database > Usage
  • GCP > SQL > Database > Usage > Limit
  • GCP > SQL > Enabled
  • GCP > SQL > Instance > Active
  • GCP > SQL > Instance > Active > Age
  • GCP > SQL > Instance > Active > Last Modified
  • GCP > SQL > Instance > Approved
  • GCP > SQL > Instance > Approved > Regions
  • GCP > SQL > Instance > Approved > Usage
  • GCP > SQL > Instance > Backup Configuration setting
  • GCP > SQL > Instance > Binary Log setting
  • GCP > SQL > Instance > CMDB
  • GCP > SQL > Instance > Data Protection
  • GCP > SQL > Instance > Data Protection > Managed Backups
  • GCP > SQL > Instance > Data Protection > Managed Backups > Minimum Schedule
  • GCP > SQL > Instance > Data Protection > Managed Backups > Schedule
  • GCP > SQL > Instance > Labels
  • GCP > SQL > Instance > Labels > Template
  • GCP > SQL > Instance > Regions
  • GCP > SQL > Instance > Usage
  • GCP > SQL > Instance > Usage > Limit
  • GCP > SQL > Labels Template [Default]
  • GCP > SQL > Permissions
  • GCP > SQL > Permissions > Levels
  • GCP > SQL > Permissions > Levels > Modifiers
  • GCP > SQL > Regions [Default]
  • GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > SQL
  • GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-sql
  • GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-sql

Action Types

  • GCP > SQL > Backup > Delete
  • GCP > SQL > Backup > Router
  • GCP > SQL > Database > Delete
  • GCP > SQL > Database > Router
  • GCP > SQL > Instance > Create Instance Backup
  • GCP > SQL > Instance > Delete
  • GCP > SQL > Instance > Delete Instance Backup
  • GCP > SQL > Instance > Router
  • GCP > SQL > Instance > Set Backup Configuration
  • GCP > SQL > Instance > Set Binary Log
  • GCP > SQL > Instance > Set Labels
  • GCP > SQL > Set API Enabled