fix: Enable EventBridge rules/targets before EKS cluster

[vchintal]

Description

The eventbridge target for the rule eks-api-endpoint-create wasn't getting created with the first terraform apply command and it doesn't get created until after the EKS cluster is completely setup causing the initial ENI create events to be missed.

This PR ensures that the first terraform apply command:

1. Includes the target module.eventbridge that takes care of creating both modules module.create_eni_lambda and module.delete_eni_lambda
2. For the above to be possible, it removes the dependency of module.delete_eni_lambda on module.eks

How was this change tested?

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Yes, I ran pre-commit run -a with this PR

[askulkarni2]

@vchintal please see the error in the CI check.

[vchintal]

@vchintal please see the error in the CI check.

Hi @askulkarni2, it is a known issue unfortunately. Since we do not run all of the TF at once, we cannot expect the TF plan to succeed.

If you see in the README we have broken this up into two TF apply commands. If the first command is run and then the TF plan is run, it will succeed. Let me know if this explanation makes sense.

[askulkarni2]

Gotcha. Can you please update the github workflow to skip this blueprint then?

[vchintal]

@askulkarni2 Sure, can do! Can you please point me to where I have to make the necessary changes? I haven't done this before and do not want to assume.

[askulkarni2]

Sure, it would just be under https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/main/.github/scripts/plan-examples.py.

[vchintal]

@askulkarni2 Think I have done it right, please check the latest commit. Thanks 🙏🏼