Skip to content

Releases: gagoar/invoke-aws-lambda

Release v3.4.0

06 Aug 12:55
Compare
Choose a tag to compare

Changes in this Release:

the biggest change here will be the runtime on the action to node 20.
some other libraries have changed to reflect security updates, but none changed the binary used to run the action.

thanks, to @igors for the PR and @schammah for the help and pinging me promptly ❤️

Release v3.3.2

20 Jan 23:16
911df9a
Compare
Choose a tag to compare

Changes in this Release

Release v3.3.1

13 May 20:20
da18fa6
Compare
Choose a tag to compare

Changes in this Release

Release v3.3.0

05 Jul 05:18
d3a63cc
Compare
Choose a tag to compare

Changes in this Release
Previously, failed Lambda invocations would be reported as successful.

adding HTTP_TIMEOUT and MAX_RETRY

26 Jun 05:47
Compare
Choose a tag to compare

This new version provides access to 2 useful configuration options:

  • AWS.config.httpOptions.timout: Returns the maximum amount of retries to perform for a service request. By default this value is calculated by the specific service object that the request is being made to. (more info )

  • AWS.config.maxRetries: Sets the socket to timeout after timeout milliseconds of inactivity on the socket. Defaults to two minutes (120000) (more info

AWS Lambda invoke

26 May 04:28
Compare
Choose a tag to compare

AWS Lambda invoke

21 May 05:30
Compare
Choose a tag to compare

AWS Lambda invoke

21 May 05:19
Compare
Choose a tag to compare

This action allows you to invoke a lambda and if needed, return a response.