alarm names should be unique

[SevereOverfl0w]

terraform doesn't complain about the conflict, but the alarms will constantly have their dimension overwritten with every deploy if the names aren't unique.

[osterman]

100% agree. We should be using the terraform-null-label module here.

[osterman]

Any chance you have time to submit a PR for this @SevereOverfl0w ?

[SevereOverfl0w]

Potentially, I'll drop a note here if I find the time and start working on it. It is a problem for us as we have multiple dbs, so I'll be inclined to fix it at some point.

[rebelthor]

Until a better solution is implemented, I've added unicity based on instance ID via PR #10

[RoryKiefer]

.... just add the rds_instance_id in front of the alarm name with a dash

in local testing, it fixes the issue:
alarm_name: "swap_usage_too_high" => "clutchwh-swap_usage_too_high" (forces new resource)

[SnufflesC137]

This can be easily fixed by including the instance id before the alarm name, example:

alarm_name = "${var.db_instance_id}_cpu_utilization_too_high"