It will generate variables even if those variables are commented out.

Example:

  # custom_rules {
  #   name      = "IPWhitelist"
  #   priority  = 1
  #   rule_type = "MatchRule"

  #   match_conditions {
  #     match_variables {
  #       variable_name = "RemoteAddr"
  #     }

  #     operator           = "IPMatch"
  #     negation_condition = true
  #     match_values       = var.whitelisted_ips
  #   }

  #   action = "Block"
  # }

Variable definition will be generated for whitelisted_ips - something I'm not expecting.

The software is not recognized unless you run it in the directory where it's installed (which means you'd need all the Terraform files in that exact location) or type out the entire directory where it's installed C:\Programs..\terraform-variables-gererator\terraform-vairbales-generator.exe. For some reason it won't be recognized as an env variable.

Add support for parsing and writing with hcl2 syntax.
We may switch to https://github.com/hashicorp/terraform-config-inspect that supports both.

Writing this here since the fork doesn't have issues enabled.

@hanks why can't differences from your fork be merged upstream?

@hanks also you are committing vendors/ directory when you shouldn't. Let dep ensure recreate it based off the Gopkg.lock.