looking into the failing test on master

Question

white-airport-8778 · Answer

I think this should fix it <https github com infracost infracost commit bd065052df385a76e00eae5035a89b0e5bb260de>

white-airport-8778 · Answer

<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

little-author-61621 · Answer

I think we should file an issue in the provider repo The AWS provider has `skip ` options for other AWS calls that don t need creds in case you don t have permissions e g `skip get ec2 platforms` This new change requires permission for DescribeTags call so maybe they can add something to allow that to be skipped

little-author-61621 · Answer

And maybe until we get an answer we can lock our tests to 3 50 but not sure what to do about demo

white-airport-8778 · Answer

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 · Answer

here s the comment <https github com hashicorp terraform provider aws pull 10807 issuecomment 885713337> to hashi

little-author-61621 · Answer

I would consider adding it as a new issue so it can go through proper triaging I think that contribution was a community contribution