lambda-notify_slack and log group /aws/lambda/notify_slack already exists when calling module multiple times about terraform-aws-notify-slack HOT 8 CLOSED

This can be solved by passing two different names to the module using the ‘lambda_function_name’ parameter

from terraform-aws-notify-slack.

Would be great to be able to pass multiple channel configs as a list of objects like so...

slack_channels = [
    {
        channel = ...
        username = ...
        etc.. = etc..
    }]

Not sure I see a need to create a lambda per channel, but that could be abstracted to the module implementation and not the root module.

from terraform-aws-notify-slack.

Thanks. I also noticed IAM already exist issues when executing in 2 different regions

from terraform-aws-notify-slack.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-notify-slack.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-notify-slack.

This issue was automatically closed because of stale in 10 days

from terraform-aws-notify-slack.

FWIW I solved the problem on my side using a custom value in lambda_function_name. A similar answer has been downvoted above

from terraform-aws-notify-slack.

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

from terraform-aws-notify-slack.