aws-core-utils
Advanced tools
Changelog
8.1.1
api-lambdas
and other-lambdas
modules:
succeedLambdaCallback
and failLambdaCallback
functions to return promises of the callback resultssucceedLambdaCallback
and failLambdaCallback
functions in an attempt to catch and
resolve issues encountered where callback is not being invokedChangelog
8.1.0
api-lambdas
module:
postConfigure
function, which can be configured onto context.handler
, that can be
used by an AWS Lambda handler
to add any additional configuration needed to the context AFTER the primary
configuration of the context has completed and BEFORE the main function is executedcontext
failure casesstringify
function to better survive responses with circular dependenciesother-lambdas
module:
postConfigure
function, which can be configured onto context.handler
, that can be
used by an AWS Lambda handler
to add any additional configuration needed to the context AFTER the primary
configuration of the context has completed and BEFORE the main function is executedcontext
failure casesstringify
function to better survive responses with circular dependenciesstages
module:
logging
property or the legacy loggingOptions
propertylogging
property or the legacy loggingSettings
propertycontexts
module:
staging
property or the legacy stagingOptions
propertystaging
property or the legacy stagingSettings
propertycustom
property or the legacy customOptions
propertycustom
property or the legacy customSettings
propertyChangelog
8.0.2
aws-sdk
dev dependency to match latest used in AWS LambdaChangelog
8.0.0
api-lambdas
module:
succeedCallback
function - replaced by succeedLambdaCallback
functionfailCallback
function - replaced by failLambdaCallback
functionfailCallbackForApiGateway
function - replaced by failLambdaCallback
functionuseLambdaProxy
, defaultHeaders
& allowedHttpStatusCodes
properties and toErrorResponse
function from
the opts
argument of the generateHandlerFunction
function in favour of rather configuring these properties via
the generateHandlerFunction
function's existing createSettings
& createOptions
argumentsopts
from the configureHandlerContext
function in favour of rather configuring its properties via the
function's existing createSettings
& createOptions
argumentsallowedHttpStatusCodes
argument of the generateHandlerFunction
function -
i.e. any code still using legacy 5th to 9th parameters: logRequestResponseAtLogLevel
, allowedHttpStatusCodes
,
invalidRequestMsg
, failureMsg
& successMsg
(instead of opts
) will now ignore any allowedHttpStatusCodes
argumentother-lambdas
module:
toErrorResponse
function from the opts
argument of the generateHandlerFunction
function in favour of
rather configuring the generateHandlerFunction
function with the toErrorResponse
function (and others) via its
existing createSettings
argumentopts
from the configureHandlerContext
function in favour of rather configuring its toErrorResponse
function via the configureHandlerContext
function's existing createSettings
argumentlambdas
module:
failCallback
function - replaced by failLambdaCallback
& other functions of the
other-lambdas
module.npmignore
release_notes.md
to CHANGES.md
Changelog
7.2.0
api-lambdas
module:
preSuccessCallback
function to be run before succeeding the Lambda callbackpreFailureCallback
function to be run before failing the Lambda callbackfailLambdaCallback
and succeedLambdaCallback
functions added in 7.1.0other-lambdas
module:
preSuccessCallback
function to be run before succeeding the Lambda callbackpreFailureCallback
function to be run before failing the Lambda callbackfailLambdaCallback
and succeedLambdaCallback
functions added in 7.1.0Changelog
7.1.0
api-lambdas
module:
succeedLambdaCallback
and failLambdaCallback
functions with cleaner parameters needed by custom
toErrorResponse
functionssucceedCallback
and failCallback
functionsgenerateHandlerFunction
to use new succeedLambdaCallback
and failLambdaCallback
functions insteadother-lambdas
module, which is a simplified version of api-lambdas
, for generating handler functions
for "other" AWS Lambdas that are NOT exposed via API Gateway