Detect & correct Compute snapshots exceeding max age

Overview

Compute snapshots can be quite costly to retain, it is also likely that after a certain point in time they're no longer required and should be cleaned up to prevent further costs.

This query trigger detects unused health checks and then either sends a notification or attempts to perform a predefined corrective action.

Getting Started

By default, this trigger is disabled, however it can be configured by setting the below variables

compute_snapshots_exceeding_max_age_trigger_enabled should be set to true as the default is false.
compute_snapshots_exceeding_max_age_trigger_schedule should be set to your desired running schedule
compute_snapshots_exceeding_max_age_default_action should be set to your desired action (i.e. "notify" for notifications or "delete_snapshot" to delete the snapshot).

Then starting the server:

flowpipe server

or if you've set the variables in a .fpvars file:

flowpipe server --var-file=/path/to/your.fpvars

Pipeline

Correct Compute snapshots exceeding max age

Query

select
  concat(name, ' [', location, '/', project, ']') as title,
  name,
  _ctx ->> 'connection_name' as cred,
  project
from
  gcp_compute_snapshot
where
  date_part('day', now() - creation_timestamp) > 15;

Schedule

15m