Skip to content
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

fix(stepfunctions-tasks): LambdaInvoke - explicit null is not passed to lambda #16721

Closed
wants to merge 1 commit into from

Conversation

jaresuth
Copy link

fixes (stepfunctions-tasks): LambdaInvoke - explicit null is not passed to lambda
Closes 16253

@gitpod-io
Copy link

gitpod-io bot commented Sep 29, 2021

@mergify
Copy link
Contributor

mergify bot commented Sep 29, 2021

Title does not follow the guidelines of Conventional Commits. Please adjust title before merge.

@jaresuth jaresuth changed the title fix (stepfunctions-tasks): LambdaInvoke - explicit null is not passed to lambda fix(stepfunctions-tasks): LambdaInvoke - explicit null is not passed to lambda Sep 29, 2021
@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildProject89A8053A-LhjRyN9kxr8o
  • Commit ID: 2d49100
  • Result: FAILED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(stepfunctions-tasks): LambdaInvoke - explicit null is not passed to lambda when using
2 participants