Table: make_team
Teams are containers that contain scenarios and data accessible only by the members of the team.
Key columns
- Provide a numeric
id
if you want to query for a specific Team. - Provide a numeric
organization_id
to query Teams for a specific Organization. This can be either set directly in awhere
clause, or specified as part ofjoin
with another table.
Examples
List of all Teams in the account
-- with Organization name embeddedselect t.id, o.name || ' -> ' || t.name as namefrom make_organization o join make_team t on t.organization_id = o.idorder by name;-- or a simplified version with own columns onlyselect id, namefrom make_teamorder by name;
List of all Teams in an Organization
select id, namefrom make_teamwhere organization_id = 1order by name;
Detail of a Team
select id, name, organization_idfrom make_teamwhere id = 1;
Schema for make_team
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
id | bigint | = | The Team ID. |
name | text | The name of the Team. | |
organization_id | bigint | The ID of the Organization. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
title | text | The display name for the resource. |