Open jordiclariana opened 4 years ago
I think the terraform json syntax is preferred for machine generated code. That would be much easier to implement than going back to HCL2.
hey @danieladams456 , that is true but it is still a good idea to have the option to convert the dict back to hcl2. In my use case, I am not converting all my tf
files to json
just one or two of those.
It would be great to have possibility to write HCL back to a file. Imagine one wants to parse something during CI/CD phase and commit it back to GitHub after, while still having neat HCL code. Not a nasty JSON :)
+1 for having this feature. It would be great to have this feature as you say, but from what I see here:
The comments are simply ignored, so we can't really combine an updated file from the dict
object.
The only solution which can do correct manipulation is the official Go library - https://github.com/hashicorp/hcl/tree/hcl2 .
Please correct me if I am wrong and you know another solution (preferably in Python).
+1
In my case, I want to dynamically update a tfvars
file and create a PR using a custom bot.
ChatGPT brought me here. It keeps suggesting I use hcldumps to convert the json back to HCL - no doubt because of this thread. :D
This is my current work around https://nklya.medium.com/how-to-write-hcl2-from-python-53ac12e45874
any news here? :)
any news here?
Is there any plan to support going backwards (from dict to hcl2)? Something like this: