Use Case: As a Platform Engineer, I want to define the mapping between Terraform variables and meshStack Building Block inputs (including source types like User Provided, Tenant ID etc.) via a YAML file in the Git repository of the terraform module.

This means, I just put e.g. a file next to my .tf files to pre-configure the meshStack BB definition.

Value: This would enable a "Configuration as Code" approach for BB definitions, making it easier to version-control the interface alongside the implementation and reducing manual configuration steps in the meshStack Admin UI.

Import of terraform repos into meshStack BB definitions could skip the mapping step in the UI and read it from the mapping file instead.

Value Created:

* GitOps Workflow: Enables "Configuration as Code" for Building Block definitions.

* Consistency: Ensures that every time a module is imported or updated, the input mapping is already predefined by the module author.

* Efficiency: Reduces manual configuration errors in the meshStack Admin Area.

* "meshStack-enabled": Terraform modules could very easily be extended in out-of-the-box BB definition (e.g. in the meshStack hub) to be consumed in one go