We would like support added for IaCM workspaces to specify files that are cloned into the /harness/ dir at IaCM stage init, but not passed to the tofu/tf cli, that could then be referenced by underlying .tf files to read that file in as input. This would be in addition to existing variable file functionality. This would enable support for different language types besides tfvars and json, such as YAML. It would then be up to the developer of the HCL to write logic to read this file from the file system and do with it as they wish: read it in and parse to variables, use a template for writing files to different systems, etc. This could also be used to pull additional tf files from other source locations as well.

This would further allow customized workspace setups where the main workspace files can live in location, while allowing for additional files managed in other source repositories to also be added for re-usability, distributed inputs/ownership, etc.