Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
aws-core-utils
Advanced tools
aws-core-utils - npm Package Versions
byron-dupreez
published 7.0.12 • Changelog
7.0.12
- Added an optional
toErrorResponsefunction to theoptsarguments offailLambdaCallbackandgenerateHandlerFunctionfunctions of theapi-lambdasmodule to enable callers to customise the error response object or Lambda Proxy error response body returned - Updated
core-functionsdependency to version 3.0.22 - Updated
logging-utilsdependency to version 4.0.22 - Updated
aws-sdkdev dependency to version 2.190.0
byron-dupreez
published 7.0.11 • Changelog
7.0.11
- Updated
core-functionsdependency to version 3.0.20 - Updated
logging-utilsdependency to version 4.0.20 - Updated
aws-sdkdev dependency to version 2.161.0 - Updated
aws-core-test-utilsdev dependency to version 3.0.7
byron-dupreez
published 7.0.10 • Changelog
7.0.10
- Renamed dummy first exports (
exports._ = '_'; //IDE workaround) of most modules to (exports._$_ = '_$_';) to avoid potential future collisions withlodash&underscore - Updated
core-functionsdependency to version 3.0.19 - Updated
logging-utilsdependency to version 4.0.19 - Updated
aws-core-test-utilsdev dependency to version 3.0.6
byron-dupreez
published 7.0.9 • Changelog
7.0.9
- Changed
dynamodb-doc-client-cache,kinesis-cache,kms-cache&lambda-cachemodules to use an optional, alternative AWS constructor passed via a new optionalcontext.AWSproperty to enable use of an AWS XRay-captured AWS constructor - Updated
aws-sdkdependency to version 2.143.0
byron-dupreez
published 7.0.8 • Changelog
7.0.8
- Updated
core-functionsdependency to version 3.0.18 - Updated
logging-utilsdependency to version 4.0.18
byron-dupreez
published 7.0.7 • Changelog
7.0.7
- Changes to
api-lambdasmodule to support API Gateway Lambda Proxy integration:- Replaced legacy 5th to 9th parameters of
generateHandlerFunctionfunction with a preferred single optionalopts5th parameter, which includes the 5 legacy parameters (logRequestResponseAtLogLevel,allowedHttpStatusCodes,invalidRequestMsg,failureMsg&successMsg) and also includes 2 new parameters (useLambdaProxy&defaultHeaders)- Note that the
generateHandlerFunctionfunction still supports invoking it with its legacy 5th to 9th parameters
- Note that the
- Replaced legacy 6th parameter of
failCallbackfunction with a preferred optionalopts6th parameter, which includes the legacy parameter (allowedHttpStatusCodes) and also includes 2 new parameters (useLambdaProxy&defaultHeaders)- Note that the
failCallbackfunction still supports invoking it with its legacy 6th parameter
- Note that the
- Changed
failCallbackfunction to also support Lambda Proxy integration - Added a new
succeedCallbackfunction to support both default integration & Lambda Proxy integration - Changed inner
handlerfunction to use newsucceedCallbackfunction & to pass thegenerateHandlerFunctionfunction's newoptsparameter on allfailCallback&succeedCallbackcalls - Setting the new
useLambdaProxyparameter totrue:- Enables your Lambda to be called from API Gateway using its Lambda Proxy integration mode
- Changes the
failCallback& newsucceedCallbackfunctions to invoke your Lambda's callback function with ONLY a null "error" parameter and a non-null "data" parameter, which is compatible with Lambda Proxy integration
- Replaced legacy 5th to 9th parameters of
- Fixed unbound logger issues in logging in
dynamodb-doc-client-cache,kinesis-cache,kms-cache,lambda-cache®ionsmodules - Updated
core-functionsdependency to version 3.0.17 - Updated
logging-utilsdependency to version 4.0.17 - Updated
aws-core-test-utilsdev dependency to version 3.0.5 - Updated
aws-sdkdev dependency to version 2.128.0
byron-dupreez
published 7.0.6 • Changelog
7.0.6
- Changes to
regionsmodule:- Changed behaviour of
getRegionKeyfunction to EITHER get the existing region key (if any) OR return undefined and NOT set a new region key (if none) - Added new
getOrSetRegionKeyfunction that gets the existing region key (if any) or sets a new region key (if none) - Added new
listRegionKeysfunction to list the currently cached region keys
- Changed behaviour of
- Changes to
dynamodb-doc-client-cache,kinesis-cache,kms-cache&lambda-cache:- Synchronised code to handle changes in
regions.getRegionKeybehaviour and to use newregions.getOrSetRegionKey - Added new
clearCachefunction to clear the instance & options caches according to the currently cached region keys
- Synchronised code to handle changes in
byron-dupreez
published 7.0.5 • Changelog
7.0.5
- Changes to
lambdasmodule:- Added new
getInvokedFunctionNameWithAliasOrVersionfunction - Changed the
getFunctionNameVersionAndAliasfunction to also return aninvokedproperty containing the same concatenation of invoked function name & alias or version generated bygetInvokedFunctionNameWithAliasOrVersion
- Added new
- Changes to
type-defsmodule:- Added new
invokedproperty toLambdaFunctionNameVersionAndAliastype definition
- Added new
- Changes to
lambda-utilsmodule:- Replaced uses of deprecated
Promises.wrapMethodwithPromises.wrap
- Replaced uses of deprecated
- Replaced all logging of
error.stackwith logging of just the error - Updated
core-functionsdependency to version 3.0.15 - Updated
logging-utilsdependency to version 4.0.14
byron-dupreez
published 7.0.4 • Changelog
7.0.4
- Changed almost all modules' exports to modifications of the default
exportsobject instead of replacing the defaultmodule.exportsobject - Added dummy first exports (
exports._ = '_'; //IDE workaround) to most modules as a temporary workaround for IDE issue - Updated
core-functionsdependency to version 3.0.14 - Updated
logging-utilsdependency to version 4.0.13
byron-dupreez
published 7.0.3 • Changelog
7.0.3
- Updated
core-functionsdependency to version 3.0.11 - Updated
logging-utilsdependency to version 4.0.11