Correct AlloyDB instances exceeding max age

Overview

AlloyDB instances can be costly to run, especially if they're rarely used, instances exceeding a certain age should be reviewed to determine if they're still required.

This pipeline detects AlloyDB instances exceeding a certain age and then either sends a notification or attempts to perform a predefined corrective action.

Whilst it is possible to utilise this pipeline standalone, it is usually called from either:

Run the pipeline

To run this pipeline from your terminal:

flowpipe pipeline run gcp_thrifty.pipeline.correct_alloydb_instances_exceeding_max_age \
  --arg 'items=<list({
  cluster_name = string
  cred = string
  instance_name = string
  location = string
  project = string
  title = string
})>'

Use this pipeline

To call this pipeline from your pipeline, use a step:

step "pipeline" "step_name" {
  pipeline = gcp_thrifty.pipeline.correct_alloydb_instances_exceeding_max_age  
  args = {
    items = <list({
  cluster_name = string
  cred = string
  instance_name = string
  location = string
  project = string
  title = string
})>
  }
}

Params

Name	Type	Required	Description	Default
items	list({ cluster_name = string cred = string instance_name = string location = string project = string title = string })	Yes	A collection of detected resources to run corrective actions against.	-
notifier	string	Yes	The name of the notifier to use for sending notification messages.	`default`
notification_level	string	Yes	The verbosity level of notification messages to send. Valid options are 'verbose', 'info', 'error'.	`info`
approvers	list(string)	Yes	List of notifiers to be used for obtaining action/approval decisions.	`[ "default" ]`
default_action	string	Yes	The default action to use for the detected item, used if no input is provided.	`notify`
enabled_actions	list(string)	Yes	The list of enabled actions to provide to approvers for selection.	`[ "skip", "delete_alloydb_instance" ]`

Outputs