Complete zero-configuration import of Building Block Definitions from meshStack Hub
Andreas Grub
Problem / Use Case
When importing a Building Block Definition (BBD) from meshStack Hub into the meshStack Admin Panel, I still have to manually configure inputs, output types, and variable mappings — even when the Hub module already ships a
meshstack_integration.tf
file that fully describes the BBD.For example, the
version_spec
of a BBD — which defines every input, its type (user-provided, static, tenant ID, etc.), validation rules, and outputs — is already expressed in the meshstack_building_block_definition
Terraform resource inside meshstack_integration.tf
. Today, the import wizard only partially reads this information, leaving me to manually fill in the rest through the UI.This manual step is especially painful when:
- Adopting a Hub module for the first time and there are 10+ inputs to configure
- Upgrading a BBD version and needing to re-enter unchanged metadata
- Onboarding a team that doesn't know Terraform but wants to use pre-built Hub modules
- Doing a live demo where every manual click breaks the "one-click" narrative
Value / Impact
A complete, zero-configuration import that reads all fields from
meshstack_integration.tf
would:- Eliminate manual UI configuration entirely for Hub-sourced BBDs
- Reduce onboarding time from hours to minutes for teams adopting Hub modules
- Provide a compelling "one-click bootstrap" story for live demos and trials
- Ensure consistency between the Terraform definition and the Panel representation (no drift from manual re-entry)
- Automatically detect the correct input type (user-provided, static, tenant ID) from the Terraform variable's type and description — removing a common source of misconfiguration
Context / Links
- Descriptor file for Building Block definitions in Git Repos — related in-progress request; the meshStack team is already working on using meshstack_integration.tffor import prefill
- Automatically set building block input type from terraform — specific ask for auto-detecting input types
If you're hitting this today when importing Hub BBDs, reach out to our customer success team or support@meshcloud.io — we'd love to hear your specific scenario and help prioritize the missing fields.