kestra_reusable_inputs

Terraform Resource: kestra_reusable_inputs

Manages a Kestra Reusable Inputs block (EE): a named, namespace-scoped set of input definitions that flows reference via a REUSABLE_INPUTS input. Its YAML source is persisted by the API and round-tripped verbatim.

Example usage

# A reusable inputs block, referenced from flows via a REUSABLE_INPUTS input
resource "kestra_reusable_inputs" "environment" {
  reusable_inputs_id = "environment-selector"
  namespace          = "company.team"

  content = <<EOT
description: Shared environment selector for the data team's flows
inputs:
  - id: environment
    type: SELECT
    values:
      - dev
      - staging
      - prod
    defaults: dev
EOT
}

Schema

Required

• content (String) The block YAML source: an optional description and the non-empty inputs list (any input type except another REUSABLE_INPUTS, which cannot be nested). Diffs are compared semantically, so a change that only reindents, reorders keys or edits comments produces no plan and the source persisted by the API keeps its previous formatting; change a value to push a reformatted source.
• namespace (String) The namespace the block is attached to. A block defined in a parent namespace is visible to (and overridable by) child namespaces.
• reusable_inputs_id (String) The reusable inputs block id — unique per (tenant, namespace).

Optional

• tenant_id (String) The tenant id (EE). Defaults to the provider tenant when omitted; the value is captured at create time, so changing the provider tenant later does not retarget the block.

Read-Only

• revision (Number) The block revision, bumped by the API on every save.

Import

Import is supported using the following syntax:

The terraform import command can be used, for example:

terraform import kestra_reusable_inputs.environment {{tenant_id}}/{{namespace}}/{{reusable_inputs_id}}