chore: avoid benchmark collision leveraging name var (#115)

Author: iru

examples/single-account-ecs/README.md

@@ -72,7 +72,7 @@ $ terraform apply
 
 | Name | Version |
 |------|---------|
-| <a name="provider_sysdig"></a> [sysdig](#provider\_sysdig) | >= 0.5.33 |
+| <a name="provider_sysdig"></a> [sysdig](#provider\_sysdig) | 0.5.37 |
 
 ## Modules
 

modules/services/cloud-bench/main.tf

@@ -52,7 +52,7 @@ resource "random_integer" "hour" {
 }
 
 resource "sysdig_secure_benchmark_task" "benchmark_task" {
-  name     = "Sysdig Secure for Cloud (AWS) - ${local.benchmark_task_name}"
+  name     = "Sysdig Secure for Cloud (AWS) - ${local.benchmark_task_name} - ${var.name}"
   schedule = "${random_integer.minute.result} ${random_integer.hour.result} * * *"
   schema   = "aws_foundations_bench-1.3.0"
   scope    = "${local.accounts_scope_clause}${local.regions_scope_clause}"

modules/services/cloud-connector-ecs/README.md

@@ -15,8 +15,8 @@ A task deployed on an **ECS deployment** will detect events in your infrastructu
 
 | Name | Version |
 |------|---------|
-| <a name="provider_aws"></a> [aws](#provider\_aws) | >= 4.0.0 |
-| <a name="provider_sysdig"></a> [sysdig](#provider\_sysdig) | >= 0.5.33 |
+| <a name="provider_aws"></a> [aws](#provider\_aws) | 4.21.0 |
+| <a name="provider_sysdig"></a> [sysdig](#provider\_sysdig) | 0.5.37 |
 
 ## Modules