Skip to content
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

provider/aws: data source "aws_ami" is working incorrect in terraform 0.7.5 #9274

Closed
opokhvalit opened this issue Oct 7, 2016 · 6 comments
Closed

Comments

@opokhvalit
Copy link

Hi!

After upgrade to terraform 0.7.5 data source "aws_ami" is returning incorrect value. When I set most_recent value to true, data source is return OLDERS AMI instead of LATEST

Sample code:

data "aws_ami" "sl_ami_is" {
most_recent = true
owners = ["${var.aws_owner_id}"]
filter {
name = "virtualization-type"
values = ["paravirtual"]
}
filter {
name = "name"
values = ["SL-64-AmazonLnx-*"]
}
}

output "AMI ID" {
value = "${data.aws_ami.sl_ami_is.id}"
}

And results of execution this code for terraform 0.7.4 and 0.7.5
for 0.7.4

$ terraform.0.7.4 apply
data.aws_ami.sl_ami_is: Refreshing state...
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:
AMI ID = ami-3d084c2a

for 0.7.5

$ terraform apply
data.aws_ami.sl_ami_is: Refreshing state...
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:
AMI ID = ami-ffc2b395

@kwilczynski
Copy link
Contributor

@opokhvalit hi there! Thank you for bringing this to our attention! I am sorry that you have issue.

Let me look into this.

@kwilczynski
Copy link
Contributor

@opokhvalit hello again! I have resolved this in #9277.

I sincerely apologise. This regression was introduced in #9033 where I have fixed a different problem with this data source.

@stack72
Copy link
Contributor

stack72 commented Oct 7, 2016

Closed via #9277

@stack72 stack72 closed this as completed Oct 7, 2016
@opokhvalit
Copy link
Author

Thanx!

@commarla
Copy link
Contributor

commarla commented Oct 7, 2016

thanks!

@ghost
Copy link

ghost commented Apr 21, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants