Marius Tolzmann

i am closing the issue as we can nor reproduce the failing test and no feedback has been received for a while. please feel free to re-open when the issue...

Yes, we can confirm this and also can confirm it is already in our backlog to be addressed. The planned solution is to allow partial evaluated values in globals and...

Hi @cwe1ss As a work-around you can use the following code that will generate your desired configuration, it assumes that the `configuration_aliases` are always to be converted to HCL and...

@oponomarov-tu @cwe1ss We are still working on native support for HCL expressions inside of globals but sadly can not give an ETA yet. But we added the `planned` label as...

@g13013 We just also noticed we never sent a work-around for the original use-case. Sorry for missing out here. The original use-case can be generated using a similar trick of...

@cwe1ss damn terraform ;) okay the work-around to unblock you would be to use `generate_file` with string templating like in: ```hcl globals "providers" { aws = { source = "hashicorp/aws"...

Hi Michal, thanks for sharing your thoughts. I must agree that the DRYness can be improved here. There are some challenging ideas in our idea backlog on this about allowing...

Thanks for sharing... this actually helps.. in the very beginning we dropped the pure terraform approach and went to a HCL approach for code generation. The only real terraform dependency...

We are currently planning a feature called Terramate Projects which will allow us to tackle this and some other community requested features in a better way. Terramate Projects will allow...

Hi @cwe1ss, as discussed in discord, this use case makes sense for repositories managing local modules that want to benefit from code generation. Adding a possibility to orchestrate different commands...