Table: buildkite_team - Query Buildkite Teams using SQL
Buildkite Teams is a feature within Buildkite that allows for the grouping of users and pipelines. It provides a way to manage access control and permissions for pipelines based on teams rather than individual users. Buildkite Teams helps you maintain a structured and organized setup, making it easier to manage permissions and access to pipelines.
Table Usage Guide
The buildkite_team
table provides insights into Teams within Buildkite. As a DevOps engineer, explore team-specific details through this table, including members, permissions, and associated pipelines. Utilize it to uncover information about teams, such as members with specific permissions, the association between teams and pipelines, and the verification of access controls.
Examples
List all teams
Explore the organization's teams in Buildkite to understand the structure and hierarchy. This can be beneficial for administration and management, offering a clear view of the teams' arrangement.
select slug, name, idfrom buildkite_teamorder by name
select slug, name, idfrom buildkite_teamorder by name
Teams created in the last week
Explore which teams have been recently established within the past week. This can be particularly useful for administrators to stay updated on new team formations and their details.
select slug, name, id, created_atfrom buildkite_teamwhere created_at > now() - interval '7 days'order by created_at desc
select slug, name, id, created_atfrom buildkite_teamwhere created_at > datetime('now', '-7 days')order by created_at desc
Secret teams
Discover the segments that are classified as 'secret' within your Buildkite teams to enhance your understanding of privacy settings and ensure appropriate access control measures are in place.
select slug, name, id, privacyfrom buildkite_teamwhere privacy = 'secret'order by name
select slug, name, id, privacyfrom buildkite_teamwhere privacy = 'secret'order by name
Schema for buildkite_team
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
created_at | timestamp with time zone | Time when the team was created. | |
created_by | jsonb | User who created the team. | |
default | boolean | True if this is the default team. | |
description | text | Description of the team. | |
id | text | ID of the team. | |
member_id | text | =, !=, ~~, ~~*, !~~, !~~* | Unique identifier for the organization. |
name | text | Name of the team. | |
organization_slug | text | Organization slug for the team. | |
privacy | text | Privacy setting for the team, e.g. visible, secret. | |
slug | text | Slug of the team. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. |
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)" -- buildkite
You can pass the configuration to the command with the --config
argument:
steampipe_export_buildkite --config '<your_config>' buildkite_team