This message was deleted.
# contributorsb
broad-zoo-34077
07/23/2021, 9:28 AMThis message was deleted.
w
white-airport-8778
07/23/2021, 9:40 AM
I think this should fix it https://github.com/infracost/infracost/commit/bd065052df385a76e00eae5035a89b0e5bb260de
white-airport-8778
07/23/2021, 11:19 AM
https://github.com/hashicorp/terraform-provider-aws/pull/10807/files is what’s causing the AWS tests to require creds, it was added in the AWS provider 3.51.0 (latest version), I can’t find a way to work around it without creds though. what’s odd is that when aws_instance.ami is set, it shouldn’t look for a launch_template. I’d rather not lock our demo/examples to 3.50 as they won’t work for ppl who have newer versions (we use to have those issues in the past).
Any ideas?
l
little-author-61621
07/23/2021, 2:15 PM
I think we should file an issue in the provider repo. The AWS provider has
skip_skip_get_ec2_platformslittle-author-61621
07/23/2021, 2:27 PM
And maybe until we get an answer we can lock our tests to 3.50, but not sure what to do about demo.
w
white-airport-8778
07/23/2021, 2:44 PM
Good idea! I’ll follow-up with hashi and update the demo to use plan.json so it continues to work. I’ll also update infracost/internal/providers/terraform/tftest/tftest.go to lock to 3.50.
white-airport-8778
07/23/2021, 3:22 PM
[here’s the comment](https://github.com/hashicorp/terraform-provider-aws/pull/10807#issuecomment-885713337) to hashi
l
little-author-61621
07/23/2021, 3:23 PM
I would consider adding it as a new issue so it can go through proper triaging. I think that contribution was a community contribution.
👍 1
7 Views