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 compute snapshots exceeding max age 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(
    unique_id,
    ' [',
    s.resource_group,
    '/',
    s.subscription_id,
    ']'
  ) as title,
  s.name,
  s.resource_group,
  s.subscription_id,
  s.sp_connection_name as conn
from
  azure_compute_snapshot as s,
  azure_subscription as sub
where
  date_part('day', now() - time_created) > 90
  and sub.subscription_id = s.subscription_id;

Schedule