Product logo
DocsBlogPricing

@turbot/gcp-scheduler

The gcp-scheduler mod contains resource, control and policy definitions for GCP Scheduler service.

Version
5.4.0
Released On
Feb 01, 2024
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.4.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.

Policy Types

  • GCP > Scheduler > Job > Approved > Custom

5.3.3 (2023-03-27)

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.

  • 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 Guardrails. This will allow the CMDB controls to process resource deletions from Guardrails more reliably than before.

5.3.2 (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.1 (2020-10-30)

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.3.0 (2020-09-16)

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.

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.
  • We've renamed the service's default regions policy from Regions [Default] to Regions to be consistent with our other regions policies.

5.1.6 (2020-08-10)

Bug fixes

  • We’ve made improvements to our GraphQL input queries for various controls and actions. You won’t notice any differences, but things should run smoother and quicker than before.

5.1.5 (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.4 (2020-06-02)

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.3 (2020-05-13)

Bug fixes

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

5.1.2 (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.

5.1.1 (2020-04-24)

Bug fixes

  • Job resource APIs are not available until an App Engine application has been created. In this situation we now show Job Discovery controls as Invalid (not Error), signaling the need for configuration changes.

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-01)

Resource Types

  • GCP > Scheduler
  • GCP > Scheduler > Job

Control Types

  • GCP > Scheduler > API Enabled
  • GCP > Scheduler > CMDB
  • GCP > Scheduler > Discovery
  • GCP > Scheduler > Job > Active
  • GCP > Scheduler > Job > Approved
  • GCP > Scheduler > Job > CMDB
  • GCP > Scheduler > Job > Discovery
  • GCP > Scheduler > Job > Usage

Policy Types

  • GCP > Scheduler > API Enabled
  • GCP > Scheduler > Approved Regions [Default]
  • GCP > Scheduler > CMDB
  • GCP > Scheduler > Enabled
  • GCP > Scheduler > Job > Active
  • GCP > Scheduler > Job > Active > Age
  • GCP > Scheduler > Job > Active > Last Modified
  • GCP > Scheduler > Job > Approved
  • GCP > Scheduler > Job > Approved > Regions
  • GCP > Scheduler > Job > Approved > Usage
  • GCP > Scheduler > Job > CMDB
  • GCP > Scheduler > Job > Regions
  • GCP > Scheduler > Job > Usage
  • GCP > Scheduler > Job > Usage > Limit
  • GCP > Scheduler > Permissions
  • GCP > Scheduler > Permissions > Levels
  • GCP > Scheduler > Permissions > Levels > Modifiers
  • GCP > Scheduler > Regions [Default]
  • GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-scheduler
  • GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-scheduler

Action Types

  • GCP > Scheduler > Job > Delete
  • GCP > Scheduler > Set API Enabled