-
Notifications
You must be signed in to change notification settings - Fork 9.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to access private_ips list from aws_network_interface #3039
Comments
I also experienced this issue. Here's a fully contained template that reproduces this issue: provider "aws" {
access_key = "${var.AWS_ACCESS_KEY_ID}"
secret_key = "${var.AWS_SECRET_ACCESS_KEY}"
region = "us-west-2"
}
resource "aws_security_group" "demo" {
name = "demo-sg"
description = "Demo Security Group"
}
resource "aws_instance" "demo" {
ami = "ami-5189a661"
instance_type = "t2.micro"
key_name = "my_key_name"
vpc_security_group_ids = [ "${aws_security_group.demo.id}" ]
associate_public_ip_address = true
}
output "security_groups" {
# Neither of these outputs a value...
value = "${element(join(",", aws_instance.demo.vpc_security_group_ids),0)}"
#value = "${aws_instance.demo.vpc_security_group_ids}"
} |
#2157 appears to fix both of these issues |
Hey folks, since #2157 is merged these should be all fixed up. Feel free to follow up if not. 👍 |
@josh-padnick thanks for the ping - will go look |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
I'm trying to create a collection of Elastic Network Interfaces using the following code:
Those appear to get created just fine but then when I try to access the assigned private IPs on those interfaces from within a template_file I get the following error:
The template looks like following:
If I inspect the tfstate file I see the following in the attributes of the aws_network_interface:
If I try to access the private ip using
${aws_network_interface.zk_eni_pool.0.private_ips.2885130951}
then it will actually give me what I'm looking for, but I'm guessing that there is supposed to be a better way to handle this. I am running terraform 0.6.3 on OS X 10.10.4.The text was updated successfully, but these errors were encountered: