meshStack 2026.23.0 introduces backwards-incompatible changes to the meshBuildingBlock v2-preview API . As a preview API, breaking changes are expected. If you only use the GA v1 API or do not interact with meshBuildingBlocks programmatically, no action is required. Breaking changes in the v2-preview API spec.inputs and status.outputs changed from JSON arrays to keyed maps. The key field is removed from each entry; the input/output identifier is now the map key. Sensitive inputs use an embedded secret format. On POST, provide {"plaintext": "..."} instead of a plain string value. On PUT, provide {"plaintext": "..."} to update or {"hash": "sha256:..."} to confirm the existing value unchanged (drift detection). Impact on the Terraform provider Users of meshstack_building_block_v2 must upgrade to Terraform provider v0.21.0 alongside this meshStack upgrade. For any input marked as sensitive in the building block definition, replace value_string or value_code with the new value_string_sensitive or value_code_sensitive attributes. These transmit the value as an embedded secret and store it masked in Terraform state. This config is only necessary when applying new meshstack_building_block_v2 resources . Already applied resources must not be touched as they would be forced to be replaced otherwise, risking potential data loss. Users of meshstack_buildingblock (v1 resource): No provider upgrade or configuration changes are needed. Note that both meshstack_building_block_v2 and meshstack_buildingblock are going to be deprecated soon in favor of a better designed meshstack_building_block resource. Migration from those resources will be provided.
