Table: make_function
Functions in Make allow you to transform data. You use functions when mapping data from one module to another. Make offers a variety of built-in functions. On top of that, you can create your own custom functions.
Key columns
- Provide a numeric
id
if you want to query for a specific Function. - Provide a numeric
team_id
to query Functions for a specific Team. This can be either set directly in awhere
clause, or specified as part ofjoin
with another table.
Caveat
- Be careful when requesting all columns (
*
),code
, or thescenarios
column without using anid
in the query. To load this data, Steampipe will have to make one extra API request per Function returned.
Examples
List of all Functions in the account
select f.id, f.name, f.description, t.name as team_namefrom make_function f join make_team t on t.id = f.team_id;-- or a simplified versionselect id, name, descriptionfrom make_function;
List of all Functions including arguments and code
select f.id, f.name, f.description, f.args, f.code, t.name as team_namefrom make_function f join make_team t on t.id = f.team_id;
Schema for make_function
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form, e.g. connection_name. | |
args | text | The Function arguments. | |
code | text | The source code of the Function. | |
created_at | timestamp with time zone | The date and time of when the Function was created. | |
created_by_user | jsonb | Function author. | |
description | text | The description of the Function. | |
id | bigint | = | The Function ID. |
name | text | The name of the Function. | |
scenarios | jsonb | The IDs and names of Scenarios, where the Function is used. | |
team_id | bigint | Virtual column, used to map the entity to another object. | |
title | text | The display name for the resource. | |
updated_at | timestamp with time zone | The date and time of when the Function was updated. |