Table: heroku_addon - Query Heroku Add-ons using SQL

Heroku Add-ons are services that support, enhance, and extend the functionality of Heroku applications. They offer a wide range of services from data storage to email services, and from log analytics to performance monitoring. Each add-on is associated with an app and can be managed through the Heroku Dashboard or CLI.

Table Usage Guide

The heroku_addon table provides insights into add-ons within Heroku. As a developer or system administrator, explore add-on-specific details through this table, such as the associated app, plan, and configuration. Utilize it to manage and optimize the add-ons for your Heroku applications.

Important Notes

Get queries require an add-on id.
Pagination is not currently supported for this resource type in the SDK.

Examples

List all add-ons

Explore all the additional features currently available in your system, understanding their status and the plans they are associated with, along with their web URLs. This can help you manage your resources better and plan for future enhancements.

select
  name,
  state,
  plan,
  web_url
from
  heroku_addon;

select
  name,
  state,
  plan,
  web_url
from
  heroku_addon;

List all provisioned add-ons

Explore which add-ons have been provisioned for your Heroku applications. This can help you manage resources effectively and understand the current state of your application's functionality.

select
  name,
  state,
  plan,
  web_url
from
  heroku_addon
where
  state = 'provisioned';

select
  name,
  state,
  plan,
  web_url
from
  heroku_addon
where
  state = 'provisioned';

List add-ons that have not changed for 30 days or more

Explore add-ons that have remained unmodified for a month or more. This is useful to identify dormant resources that might be candidates for review or removal to optimize resource usage.

select
  name,
  web_url,
  updated_at
from
  heroku_addon
where
  updated_at < now() - interval '30 days';

select
  name,
  web_url,
  updated_at
from
  heroku_addon
where
  updated_at < datetime('now', '-30 days');

Schema for heroku_addon

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
account_id	text	=, !=, ~~, ~~, !~~, !~~	Unique identifier of an account.
actions	jsonb		Provider actions for this specific add-on.
addon_service	jsonb		Identity of add-on service.
app	jsonb		Billing application associated with this add-on.
billed_price	jsonb		Billed price.
billing_entity	jsonb		Billing entity associated with this add-on.
config_vars	jsonb		Config vars exposed to the owning app by this add-on.
created_at	timestamp with time zone		When add-on was created.
id	text	=	Unique identifier of add-on.
name	text		Globally unique name of the add-on.
plan	jsonb		Identity of add-on plan.
provider_id	text		Id of this add-on with its provider.
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
state	text		State in the add-on's lifecycle.
updated_at	timestamp with time zone		When add-on was updated.
web_url	text		URL for logging into web interface of add-on (e.g. a dashboard).

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- heroku

You can pass the configuration to the command with the --config argument:

steampipe_export_heroku --config '<your_config>' heroku_addon