You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -38,7 +38,6 @@ Edit the values of your parameter in SSM Parameter Store to use the failure inje
38
38
*`isEnabled: false` means that the failure injection module is disabled and no failure is injected.
39
39
*`failureMode` selects which failure you want to inject. The options are `latency`, `exception` or `statuscode` as explained below.
40
40
*`rate` controls the rate of failure. 1 means that failure is injected on all invocations and 0.5 that failure is injected on about half of all invocations.
41
-
*`catchException` specifies whether to catch any thrown exceptions or to pass them through to Lambda (**default** is false)
42
41
*`minLatency` and `maxLatency` is the span of latency in milliseconds injected into your function when `failureMode` is set to `latency`.
43
42
*`exceptionMsg` is the message thrown with the exception created when `failureMode` is set to `exception`.
44
43
*`statusCode` is the status code returned by your function when `failureMode` is set to `statuscode`.
@@ -58,9 +57,9 @@ Inspired by Yan Cui's articles on latency injection for AWS Lambda (https://hack
58
57
59
58
## Changelog
60
59
61
-
### 2020-02-08 v0.1.1
60
+
### 2020-02-13 v0.1.1
62
61
63
-
*Added a flag to determine whether to catch or release errors before they reach AWS Lambda
62
+
*Fixed issue with exception injection not throwing the exception. Thanks to [Jason Barto](https://github.com/jpbarto)!
0 commit comments