Update block
PUT /api/pipelines/:pipeline_uuid/blocks/:block_uuid
Human readable block name. This is used to generate the UUID, e.g. restless dust. Names will be slugified to a safe-uuid.
Type of block:
callback, chart, conditional, custom, data_exporter, data_loader, dbt, extension, global_data_product, markdown, scratchpad, sensor, transformer
Data integration bookmark values as a list of strings.
Array of callback block objects. Same shape as blocks.
Block color displayed by the frontend for custom blocks. All other block types have predefined colors.
Miscellaneous configuration settings for the block.
The content of block formatted as a string. Use /n for newlines. Omitting will create an empty block.
The destination table for a data integration pipeline.
Array of blocks downstream from the created block.
Used when configuring a Kubernetes executor. See the Kubernetes config page for more details
Used when configuring a Kubernetes executor. See the Kubernetes config page for more details
UUID of extensions, currently Great Expectations is the only extension supported.
The block language:
python, sql, r, yaml, markdown
Array of strings containing the pipeline uuids for which the block is a member.
The configuration for block retry logic. See the pipeline runs docs for retry config examples.
The block tap stream ID for data integration pipelines.
An array of strings representing the uuids of upstream blocks (the blocks on which the new block depends). For example, ["a", "b"] will create a block that depends on blocks a and b.
The unique id of the block. This is generated from name, so it’s not necessary to populate this field.
Was this page helpful?