Table: heroku_team - Query Heroku Teams using SQL
Heroku Teams is a feature within the Heroku platform that allows users to collaborate on applications. Teams provide a shared, collaborative space where members can access, manage, and deploy applications. It offers a central point for managing access to apps, pipelines, and resources.
Table Usage Guide
The heroku_team
table provides comprehensive insights into the teams within Heroku. As an application developer or DevOps engineer, you can use this table to explore details about each team, including its members, associated applications, and limits. This can be particularly useful for managing access to applications, tracking team usage, and ensuring compliance with organizational policies.
Important Notes
- Get queries require a team
id
. - Pagination is not currently supported for this resource type in the SDK.
Examples
List all teams
Explore which teams are available and their types to understand the structure and organization within your Heroku environment. This can assist in managing team resources and ensuring appropriate access and permissions.
select name, team_typefrom heroku_team;
select name, team_typefrom heroku_team;
Find the default team
Analyze the settings to understand which team has been set as the default in your Heroku application. This can help streamline team management and ensure proper access controls are in place.
select name, team_typefrom heroku_teamwhere is_default;
select name, team_typefrom heroku_teamwhere is_default = 1;
Schema for heroku_team
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
account_id | text | =, !=, ~~, ~~*, !~~, !~~* | Unique identifier of an account. |
created_at | timestamp with time zone | When the team was created. | |
credit_card_collections | boolean | Whether charges incurred by the team are paid by credit card. | |
enterprise_account | jsonb | Enterprise Account associated with the team. | |
id | text | = | Unique identifier of team. |
identity_provider | jsonb | Identity Provider associated with the team. | |
is_default | boolean | Whether to use this team when none is specified. | |
membership_limit | double precision | Upper limit of members allowed in a team. | |
name | text | Unique name of team. | |
provisioned_licenses | boolean | Whether the team is provisioned licenses by salesforce. | |
role | text | Role in the team. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
team_type | text | Type of team. | |
updated_at | timestamp with time zone | When the team was updated. |
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_team