Provisioner IP address access with count > 1

[Kale Franz]

Following the local-exec provisioner documentation, I'd like to create three ec2 instances.  Here's the modified appropriate syntax as far as I can tell:

resource "aws_instance" "web" {
    ...
    count = 3
    provisioner "local-exec" {
        command = "echo ${element(aws_instance.web.*.private_ip, count.index)} >> private_ips.txt"
    }
}

When planning or applying, I get the following error:

* aws_instance.web: connection info cannot contain splat variable referencing itself

Any ideas on how to make this example work?

More fundamentally, I'm trying to work out using ansible (executed locally) as a provisioner. Any general advice or pointers would be much appreciated!

[Paul Hinze]

Hey Kale,

From a provisioner you can reference an attribute from the current resource by using ${self.attr} [1].

Give this a try:

    provisioner "local-exec" {
        command = "echo ${self.private_ip} >> private_ips.txt"
    }

Hope this helps!

Paul

[1] https://terraform.io/docs/configuration/interpolation.html

--
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 post to this group, send email to terrafo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/6534f14a-6fb5-4813-93de-7459ae4f1dc6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kale Franz]

Perfect. Exactly what I needed. Thanks!

[Ioannis Polyzos]

Hi Paul, 

  I have similar case with OpenStack provider. I would like to list ALL the private IP addresses of my instances and pass them to a remote script.  

  How you would advice aproach such scenario?

Regards, 

Ioannis

[Paul Hinze]

Ioannis,

We're planning better core support for this scenario down the road, but for now there's a workaround with "null_resource" - a resource that does nothing but allow you to place provisioners at certain points in the dependency graph.

Here's the idea:

resource "openstack_compute_instance_v2" "foo" {

  count = 5

  // ...
}

resource "null_resource" "foo_provisioning" {

  provisioner "local-exec" {

    command = "provision-all-instances.sh ${join(" ", openstack_compute_instance_v2.foo.*.access_ip_v4)}"

  }

}

Hopefully that points you in the right direction!

Paul

To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/df7d21ad-5c69-46a2-b7c0-f77f1fe571f1%40googlegroups.com.