feat(event_source): add CodeDeploy Lifecycle Hook event

[mw-root]

Issue number: #5171

Summary

This is a simple change to implement the lambda event type CodeDeployLifeCycleHookLambdaEvent.

This event only provides DeploymentId and LifecycleEventHookExecutionId (at least in my experience)

Changes

This adds a new DictWrapper inherited class to define the properties passed by CodeDeployment.

User experience

This allows users to use the new class as an event type in their lambda handler

from aws_lambda_powertools.utilities.data_classes import (
  event_source,
  CodeDeployLifeCycleHookEvent,
)

def lambda_handler(
    event: CodeDeployLifeCycleHookEvent, context: LambdaContext
) -> None:
  ...

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

This is new functionality and is not a breaking change.

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.21%. Comparing base (32061f0) to head (1a56c94).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #5219   +/-   ##
========================================
  Coverage    96.21%   96.21%           
========================================
  Files          228      229    +1     
  Lines        10746    10755    +9     
  Branches      2001     2003    +2     
========================================
+ Hits         10339    10348    +9     
  Misses         321      321           
  Partials        86       86           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mw-root]

Oh duh, I'll add tests.

[leandrodamascena]

Hey @mw-root! Thanks a lot for working and fixing this PR! Everything looks great for me, we just need to this new class in our documentation. If you have problems to run the documentation locally, please let me know and I can help.

[sonarqubecloud]

Quality Gate failed

Failed conditions
E Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[mw-root]

@leandrodamascena thanks again for your help.

Are docs auto-generated or should I add them by hand? I ran mkdocs build but didn't see any changes afterward.

[leandrodamascena]

Are docs auto-generated or should I add them by hand?

Our documentation is not automatically generated, but we are working on it somewhere in the near future. You need to open https://github.com/aws-powertools/powertools-lambda-python/blob/develop/docs/utilities/data_classes.md, and add an example in the example folder. Check the VPC Lattice V2 in this documentation and you'll see how to do that.

I ran mkdocs build but didn't see any changes afterward.

If you have already created the Poetry environment, you can use make docs-local. If not, use make docs-local-docker to run it in Docker.

Please let me know if you have any additional question and I can help with that.

[leandrodamascena]

Just 2 small changes and we are good to merge! Go go go!! 🚀

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[leandrodamascena]

APPROVED @mw-root! Thanks a lot for addressing all the feedback! 🥇

[mw-root]

@leandrodamascena Thanks for all your help!

[leandrodamascena]

@leandrodamascena Thanks for all your help!

We love it when we have people from the community helping us improve the project! It means the world to us.

I'm justing waiting the CI turns green to merge the PR.

[boring-cyborg]

Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience!