parameters.json
file is included at the root of the directory of a custom block. It is used to describe the block itself and identify the parameters available for its configuration. The parameters defined in this file are the input options rendered for the block in Studio and passed into the block as arguments when the it is run.
type
property. For example:
Type | Renders | Passes |
---|---|---|
Boolean | Checkbox | --<param-name> 1 (true) | --<param-name> 0 (false) |
Bucket | Dropdown | --<param-name> "<bucket-name>" |
Dataset | Dropdown | --<param-name> "<dataset-name>" |
Flag | Checkbox | --<param-name> (true) | (false) |
Float | Text box | --<param-name> <value> |
Int | Text box | --<param-name> <value> |
Secret | Text box | <param-name> (environment variable) |
Select | Dropdown | --<param-name> <value> |
String | Text box | --<param-name> "<value>" |
custom-processing-param
is passed to your feature generation function as custom_processing_param
.All parameter types rendered in Studio
Boolean parameter type rendered in Studio
Bucket parameter type rendered in Studio
Dataset parameter type rendered in Studio
Flag parameter type rendered in Studio
Float parameter type rendered in Studio
Int parameter type rendered in Studio
Secret parameter type rendered in Studio
Secret parameter type (hidden) rendered in Studio
Select parameter type without labels rendered in Studio
Select parameter type valid options without labels rendered in Studio
Select parameter type with labels rendered in Studio
Select parameter type valid options with labels rendered in Studio
String parameter type rendered in Studio
group
property is rendered as a header element.
Processing parameters grouped into two groups
showIf
property.
Parameter conditionally hidden based on another parameter
Parameter conditionally shown based on another parameter
latestImplementationVersion
property of the processing block.
A processing block set to version 4: