-
Notifications
You must be signed in to change notification settings - Fork 239
CodeCommitEvent Record #78
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
Comments
merged #79 |
Do you have a prediction of when will have a release with this changes ? |
maxday
added a commit
that referenced
this issue
Mar 18, 2025
* Profiler updates Moved profiler to 'experimental' folder Added AWS_LAMBDA_ prefix to env vars Updated README.md * fix: IAM permissions, wrapper, port communication and integration test --------- Co-authored-by: Maxime David <[email protected]>
maxday
added a commit
that referenced
this issue
Mar 18, 2025
* Profiler updates Moved profiler to 'experimental' folder Added AWS_LAMBDA_ prefix to env vars Updated README.md * fix: IAM permissions, wrapper, port communication and integration test --------- Co-authored-by: Maxime David <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The CodeCommitEvent format when a lambda is triggred is:
There is no way to access the custom data because the field is missing in the CodeCommitEvent.Record, or should I do something diffent ?
The text was updated successfully, but these errors were encountered: