KG
Size: a a a
KG
P
KG
P
KG
P
AK
НС
AK
AF
terragrunt apply-all
для двух tfvars?AD
AD
OK
data "aws_instances" "emr_instances_master" {
instance_tags = {
"environment" = dev
"aws:elasticmapreduce:instance-group-role" = "MASTER"
}
instance_state_names = ["running"]
}
resource "aws_cloudwatch_metric_alarm" "EMR-Master-High-RootDiskUtil" {
count = length(data.aws_instances.emr_instances_master[0].ids)
alarm_name = "EMR-Master-HighRootDiskUtil"
comparison_operator = "GreaterThanOrEqualToThreshold"
period = "60"
evaluation_periods = "1"
datapoints_to_alarm = 1
# second
statistic = "Maximum"
threshold = "80"
alarm_description = ""
metric_name = "disk_used_percent"
namespace = "EMR"
dimensions = {
InstanceId = "data.aws_instances.emr_instances_master[0].*.ids[count.index]"
path = "/"
fstype = "ext4"
device = "xvda1"
}
132: count = length(data.aws_instances.emr_instances_master[0].ids)
The "count" value depends on resource attributes that cannot be determined
until apply, so Terraform cannot predict how many instances will be created.
To work around this, use the -target argument to first apply only the
resources that the count depends on.
A
OK
OK
DZ
The "count" value depends on resource attributes that cannot be determined
until apply
"DZ
РР
The "count" value depends on resource attributes that cannot be determined
until apply
"РР