Pre and post deployment lifecycle hooks
- Dominant language
- No language data
- Stars
- 196
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
**Note**
> * Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
> * Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
> If you are interested in providing additional feedback, please leave a comment
**Description**
This gives customers the ability to run validation checks (health checks, smoke tests) in a function's deployment lifecycle, particularly before code/after code/configuration updates, thus providing safe deployment controls for customers. Please leave a comment so that we can reach out to you to get additional feedback.
**Additional context**
1) How do you typically roll out your changes in Lambda functions? (All-at-once, canary, blue-green)
2) How would you use lifecycle hooks in your deployment process?
3) What pre-deployment validation checks do you perform before deploying your function?
4) What post-deployment validation checks do you perform before deploying your function? (Health checks, custom validation scripts)
Contributor guide
Assessment
This issue has not been assessed yet.