Table: heroku_app - Query Heroku Apps using SQL
Heroku is a cloud platform as a service (PaaS) that lets companies build, deliver, monitor, and scale apps. Heroku is flexible for both developers and enterprises, offering add-on services, including data services, utility services, and more. The platform also supports several programming languages, including Java, Node.js, Scala, Clojure, Python, PHP, and Go.
Table Usage Guide
The heroku_app
table provides insights into the apps within Heroku. As a developer or system administrator, you can explore app-specific details through this table, including the app's unique ID, name, owner, and team. You can also gain insights into the app's stack, region, and maintenance status, which can be crucial for app maintenance, development, and scaling strategies.
Important Notes
- Get queries require an app
id
. - Pagination is not currently supported for this resource type in the SDK.
Examples
List all apps
Explore the names and web URLs of all applications within your Heroku platform. This can be useful for a quick overview of all your applications, or to find the web URL of a specific application.
select name, web_urlfrom heroku_app;
select name, web_urlfrom heroku_app;
Apps by region
Explore which regions have the most Heroku apps deployed. This can help you understand the geographical distribution of your applications and inform decisions about where to focus resources.
select region ->> 'name' as region_name, count(*)from heroku_appgroup by region_name;
select json_extract(region, '$.name') as region_name, count(*)from heroku_appgroup by region_name;
Apps that have not changed for 30 days or more
Explore which applications have remained static for over a month. This can be useful for identifying potentially outdated or unused apps that may require updates or removal.
select name, web_url, updated_atfrom heroku_appwhere updated_at < now() - interval '30 days';
select name, web_url, updated_atfrom heroku_appwhere updated_at < datetime('now', '-30 days');
Schema for heroku_app
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form, e.g. connection_name. | |
acm | text | ACM status of this app. | |
archived_at | timestamp with time zone | When app was archived. | |
build_stack | jsonb | Identity of the stack that will be used for new builds. | |
buildpack_provided_description | text | Description from buildpack of app. | |
created_at | timestamp with time zone | When app was created. | |
git_url | text | Git repo URL of app. | |
id | text | = | Unique identifier of app. |
internal_routing | boolean | Describes whether a Private Spaces app is externally routable or not. | |
maintenance | boolean | Maintenance status of app. | |
name | text | Unique name of app. | |
organization | jsonb | Identity of team. | |
owner | jsonb | Identity of app owner. | |
region | jsonb | Identity of app region. | |
released_at | timestamp with time zone | When app was released. | |
repo_size | bigint | Git repo size in bytes of app. | |
slug_size | bigint | Slug size in bytes of app. | |
space | jsonb | Identity of space. | |
stack | jsonb | Identity of app stack. | |
team | jsonb | identity of team. | |
updated_at | timestamp with time zone | When app was updated. | |
web_url | text | Web URL of app. |
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_app