<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>sali0</author><text>So much hate ITT for such a great tool. Terraform is definitely not perfect but it&amp;#x27;s still one of my favorite tools, solely because of the amount of efficiency gained from learning it. Yes HCL is not perfect, but it is definitely adequate for a lot of applications. IMO, Hashicorp makes some of the most well thought out tools and I am grateful of their attitude towards open source.</text><parent_chain></parent_chain></comment><story><title>Terraform 0.15 General Availability</title><url>https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-15-general-availability</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>ghjnut</author><text>Hijacking a bit, but does anyone have any good resources&amp;#x2F;guides around managing terraform state in larger organizations? Terraform enterprise seems to address this but I was wondering if there&amp;#x27;s workflows that allowed subsections of infrastructure (think teams or systems) and didn&amp;#x27;t rely on a re-evaluation of the entire organization&amp;#x27;s assets. So far the only approach I&amp;#x27;ve seen is having protected high level (VPC, subnets etc) as a separate state and using terraform_remote_state to reference those.</text><parent_chain></parent_chain></comment><story><title>Terraform 0.15 General Availability</title><url>https://www.hashicorp.com/blog/announcing-hashicorp-terraform-0-15-general-availability</url></story>