CodeDeploy: how to specify Lambda hooks for lifecycle events?

[finferflu]

Hi all,

I've been looking through the documentation, however, there seems to be no mention of Lambda hooks that can be triggered by lifecycle events during a CodeDeploy deployment. These seem to be vital to, e.g. run automated tests before traffic is sent to a new deployment.

Am I missing something, or is it lacking in the Terraform AWS provider? Failing that, is there anything that this provider can do to facilitate the use of AppSpec files?

Thanks!

[jpmontez]

Yeah, I noticed this too. Is this not supported by Terraform?

[harryherbig]

Are there any news on the missing features?

While researching how to establish a proper CI/CD pipeline for aws lambdas I ended up choosing CodeDeploy, mostly because of the pre traffic hooks and the automated alias switiching.
Now it looks like, that we would need to use SAM to get this feature, but this would mean, that all resources would be created with SAM and be written in CloudFormation.
For our team we agreed on terraform for IaaC, so using SAM / CF for this would mean, that we would have resources coming from two different sources, which we wanted to avoid.

[alexandergunnarson]

We've gone with using triggers (see trigger_configuration in TF docs) to emulate this functionality. Don't love that we have to use a workaround, but at least a workaround exists!

We tried this example but it didn't really work for our CD use case.

[justinretzolk]

Hey y'all 👋 Thank you for taking the time to file this issue! Given that there's been a number of AWS provider releases since you initially filed it, can you confirm whether you're still missing this functionality?

[MatthewEdwards]

I believe this is still missing functionality

[MatthewEdwards]

Upon further investigation I've found the hook needs to be added to the revision.json if you're not using the AppSpec so I believe there's nothing for the provider to do here.

{
  "version": 1,
  "Resources": [
    {
      "TargetService": {
        "Type": "AWS::ECS::Service",
        "Properties": {
          "TaskDefinition": "arn:aws:ecs:eu-west-1:<redacted>:task-definition/<redacted>",
          "LoadBalancerInfo": {
            "ContainerName": "<redacted>",
            "ContainerPort": 3000
          }
        }
      }
    }
  ],
  "Hooks": [
    {
      "BeforeAllowTraffic": "arn:aws:lambda:eu-west-1:<redacted>:<redacted>"
    }
  ]
}

[justinretzolk]

Hey @MatthewEdwards 👋 Thank you for taking the time to follow up with your findings here! Always great to see someone provide their solution in case someone else stumbles across this issue in the future 🎉.

Given your findings, I'll mark this issue as closed. If you feel we've done this in error, please open a new issue with any updated information you may have.

[github-actions]

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.