lively-helicopter-12644
02/24/2023, 11:31 AMbusy-agent-35515
02/24/2023, 11:32 AMlively-helicopter-12644
02/24/2023, 11:44 AMmysterious-teacher-68276
02/24/2023, 11:57 AMbusy-agent-35515
02/24/2023, 12:11 PMlively-helicopter-12644
02/24/2023, 12:11 PMmysterious-teacher-68276
02/24/2023, 12:17 PMcount
logic and involved it’s probably likely that there’s a bug in the Terraform parsing our side, which again is incredibly tricky to resolve without the actual code. It could be as simple as doing the following for the problem resource:
variable "change_my_name" {}
resource "aws_instance" "replace_the_name" {
count = var.change_my_name
# remove any attributes that we're not interested in
...
}
this should be pretty safe from a sec ops point of viewbusy-agent-35515
02/24/2023, 12:35 PMlively-helicopter-12644
02/24/2023, 4:42 PMmysterious-teacher-68276
02/24/2023, 4:43 PMlively-helicopter-12644
02/24/2023, 4:44 PMdata.aws_availability_zones.available.names
mysterious-teacher-68276
02/24/2023, 4:46 PMlively-helicopter-12644
02/24/2023, 4:48 PMmysterious-teacher-68276
02/24/2023, 4:49 PMlively-helicopter-12644
02/24/2023, 4:50 PMdata.aws_availability_zones
is the only one that required an accurate mock, as far as I see now. I am sure many use these for ensure all AZs in a given AWS region is covered.mysterious-teacher-68276
02/24/2023, 4:53 PMlively-helicopter-12644
02/24/2023, 4:59 PMmysterious-teacher-68276
02/24/2023, 5:01 PMlively-helicopter-12644
02/24/2023, 5:02 PM