Alternate resource type configuration

[Trevor Hartman]

In the Jsonnet post from a few years ago, the output.json example shows resources being configured like:

   "web_elb": {

      "instances": [

         "web"

      ],

      "kind": "Terraform#Aws#ElasticLoadBalancer",

      "listener": {

         "instance_port": 80,

         "instance_protocol": "http",

         "lb_port": 80,

         "lb_protocol": "http"

      },

      "name": "terraform-example-elb"

   }

This is in contrast to the documented, more rigid way of configuring resources in Terraform:

"resource": {

  "aws_elb": {

    "web_elb": {

      ...

    }

  }

}

Based on output.json I started trying to define GCP resources the same way, e.g.:

      "dev-us-central1-private-subnet": {

         "ip_cidr_range": "10.0.0.0/13",

         "kind": "Terraform#Gcp#GoogleComputeSubnetwork",

         "name": "dev-us-central1-private",

         "network": "${google_compute_network.dev.self_link}",

         "region": "us-central1"

      },

But if I try this, Terraform complains:

* Unknown root level key: dev-us-central1-private-subnet

Is this not supported? Was it an old way of doing things? It happens to be much more flexible when generating config with Jsonnet and taking advantage of nested loops and maps, so I hope it works.

Thanks.

[Dave Cunningham]

Can you paste a complete JSON example of a TF config that doesn't work -- it's probably some confusion in the process of converting HCL to JSON (which is a bit subtle sometimes).

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/terraform/issues
IRC: #terraform-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Terraform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to terraform-too...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/44ef114d-8f96-4cc1-955d-c78776a93a47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Trevor Hartman]

Here's a link to output.json from the post:

https://groups.google.com/group/terraform-tool/attach/b0c13dd3b522f924/output.json?part=0.4&authuser=1

I've switched to using generating standard TF syntax, so this isn't an issue. Just curious if it is or was possible to configure resources using "kind", e.g. "kind": "Terraform#Gcp#GoogleComputeSubnetwork", instead of nesting them inside a parent "google_compute_subnetwork" item.

[Dave Cunningham]

Ah yeah that was a proposal for an alternative JSON format that never happened.  Terraform accepts JSON in a rigid format so you have to do the "resources": { "my_name": { } } bit.  You can abstract that in Jsonnet if you like but unsure if it's worth it.

I'm curious how you're generating standard TF syntax, are you referring to HCL or the TF JSON?

To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/949992c5-4c8b-4b2f-8a61-2526ee8ca41f%40googlegroups.com.

[Trevor Hartman]

I'm generating TF JSON via jsonnet. Turns out it's not that hard or inconvenient to adhere to TF's rigid nested format using jsonnet's object concatenation.

[Dave Cunningham]

Got it!  You might find this interesting, although it's more heavyweight http://www.slideshare.net/davidcunningham739/easy-deployment-management-of-cloud-apps/11

To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/5aad37d2-8cea-4e86-a4e6-02f7094b2056%40googlegroups.com.

[Trevor Hartman]

Looks interesting! Is that Python transformation piece pure custom or did you open source anything? I'm trying to figure out how to tie this all into a CD pipeline.

You received this message because you are subscribed to a topic in the Google Groups "Terraform" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/terraform-tool/-RK1nIPkN10/unsubscribe.
To unsubscribe from this group and all its topics, send an email to terraform-too...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/CANarjTgEhcDiEPSKOAMWD3tLPD3QWvWKsykJw_Z%3DUi8ZxZ%2Bm9Q%40mail.gmail.com.

[Dave Cunningham]

It's an ongoing experiment in the jsonnet repo case_studies/micromanage that I wish I had more time to work on :)

Really high-level abstract descriptions of cloud services that are nestable and portable between cloud providers.

To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/etPan.56e305f8.20c89e9.8149%40LM-SJN-00872803.

[Ameir Abdeldayem]

FWIW, generating compliant HCL isn't that bad.  I used to generate pure JSON for TF, but for the sake of others on my team who weren't comfortable with that approach, I explored generating HCL from a hash.

The bulk of that is here, if anyone is interested:

https://github.com/ameir/terraform-php/blob/develop/src/Terraform.php#L107

To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/CANarjTgGbMMGOfjs_BEvbBGgc7BFTDgv_fst04O9UJtA2MZimg%40mail.gmail.com.

[Dave Cunningham]

I believe it'd be possible to generate HCL from Jsonnet using a "manifest" function like the ones that already exist in the standard library for emitting INI files, Python dicts, etc.  However I've never had to do that.  The only time I had a problem (putting multiple providers in the same JSON file) it was resolved by writing multiple JSON tf files and having Terraform merge them.

To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/CAAqPzm7aKJShzGoSuNwm1xWj%2BnkEE9bodGkiihEqR-Kg2PMZCQ%40mail.gmail.com.