Manual Building Blocks: SINGLE_SELECT and MULTI_SELECT inputs cause Terraform provider plan inconsistency
m
meshcloud Support
When managing a Manual Building Block definition via the meshStack Terraform provider, including inputs of type
SINGLE_SELECT
or MULTI_SELECT
causes a provider error:Provider produced inconsistent result after apply
.version_spec.outputs: new element "my_input" has appeared.
Root cause:
The Manual implementation type automatically mirrors all inputs to outputs during a run. For non-basic input types (SINGLE_SELECT
, MULTI_SELECT
), meshStack maps these to STRING
or CODE
outputs respectively. The Terraform provider does not account for this auto-generated output and reports it as an unexpected state change.Workaround:
Define only STRING
, INTEGER
, BOOLEAN
, or CODE
inputs in Manual Building Block definitions managed via Terraform. SINGLE_SELECT
and MULTI_SELECT
inputs can be used when managing the building block definition through the meshStack UI.Affects:
meshStack Terraform provider users managing Manual Building Block definitions that include SINGLE_SELECT
or MULTI_SELECT
input types.The underlying meshStack runtime fix (auto-mapping input types to valid output types) was shipped in v2026.19.0. A provider-side fix to handle the auto-generated outputs gracefully is in progress.