From c9c7c6991b59c6f70e4a8005c042bd98b8a71840 Mon Sep 17 00:00:00 2001
From: Victor Sanahuja <244157+piscue@users.noreply.github.com>
Date: Thu, 13 Jan 2022 22:48:53 +0100
Subject: [PATCH] fix(runnrs): Pool runners to allow multiple pool_config
 objects (#1621)

* Fix: pool runners to allow multiple event rules

* fix count.index in name

* multiple statement_ids
---
 modules/runners/pool/main.tf | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/modules/runners/pool/main.tf b/modules/runners/pool/main.tf
index 03c2ec474d..7de74454f7 100644
--- a/modules/runners/pool/main.tf
+++ b/modules/runners/pool/main.tf
@@ -99,7 +99,7 @@ data "aws_iam_policy_document" "lambda_assume_role_policy" {
 resource "aws_cloudwatch_event_rule" "pool" {
   count = length(var.config.pool)
 
-  name                = "${var.config.environment}-pool-rule"
+  name                = "${var.config.environment}-pool-${count.index}-rule"
   schedule_expression = var.config.pool[count.index].schedule_expression
   tags                = var.config.tags
 }
@@ -118,7 +118,7 @@ resource "aws_cloudwatch_event_target" "pool" {
 resource "aws_lambda_permission" "pool" {
   count = length(var.config.pool)
 
-  statement_id  = "AllowExecutionFromCloudWatch"
+  statement_id  = "AllowExecutionFromCloudWatch-${count.index}"
   action        = "lambda:InvokeFunction"
   function_name = aws_lambda_function.pool.function_name
   principal     = "events.amazonaws.com"