-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CodeDeploy: how to specify Lambda hooks for lifecycle events? #10440
Comments
Yeah, I noticed this too. Is this not supported by Terraform? |
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. |
We've gone with using triggers (see We tried this example but it didn't really work for our CD use case. |
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? |
I believe this is still missing functionality |
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.
|
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. |
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. |
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!
The text was updated successfully, but these errors were encountered: