In the last PR, I added more variables into the alarm description, which will help someone identify quicker what the properties/conditions of that alarm. However, some variables in Terraform can decimalize and looks insane (see below). To fix I just floor()-ed every variable.
# module.elasticsearch-alarms.aws_cloudwatch_metric_alarm.free_storage_space_too_low[0] will be updated in-place
~ resource "aws_cloudwatch_metric_alarm" "free_storage_space_too_low" {
~ alarm_description = "Minimum elasticsearch free storage space on a single node over last 10 minute(s) is too low" -> "Minimum free disk space on a single node under 7680.0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006MB for the last 10 minute(s)"
id = "master-es-search-indexes-ElasticSearch-FreeStorageSpaceTooLow"
tags = {
"Client" = "cli"
"Id" = "cli-master-es-search-indexes"
"StackVersion" = "1.0.0"
"Stage" = "master"
"Terraform" = "true"
}
# (17 unchanged attributes hidden)
}
Issue Overview
In the last PR, I added more variables into the alarm description, which will help someone identify quicker what the properties/conditions of that alarm. However, some variables in Terraform can decimalize and looks insane (see below). To fix I just
floor()
-ed every variable.