updating versions

.gitignore

@@ -106,4 +106,4 @@ dist
 # Stores VSCode versions used for testing VSCode extensions
 .vscode-test
 
-sam/samconfig.toml
+evb-local-backend/samconfig.toml

README.md

@@ -141,7 +141,7 @@ If the rule's logical ID is omitted such as `evb local --rule` the tool will par
 ## Replaying archived events
 Add `--replay` option to command. This will guide you through a wizard to find the archive and set the time range to replay.
 
-Note that this currently only works together with the `-t` flag and it requires at least v0.0.6 of the [evb-local backend](https://serverlessrepo.aws.amazon.com/applications/eu-west-1/751354400372/evb-local)
+Note that this currently only works together with the `-t` flag and it requires at least v0.0.8 of the [evb-local backend](https://serverlessrepo.aws.amazon.com/applications/eu-west-1/751354400372/evb-local)
 
 ## Forward events to sam-local
 All `evb local` commands support a `--sam-local` flag. When used, events will be passed on to sam-local for more advanced debugging

docs/dlq-handling.md

@@ -178,7 +178,7 @@ Steps:
 * `CleanUp`: Removes all temporary resources created for the replay
 * `Dispatch`: Re-puts the events on the event bus
 
-*Note that the Step Functions flow will only happen when using `--replay-speed` > 0 or replaying from an OnFailure archive. Both require the [evb-local](https://serverlessrepo.aws.amazon.com/applications/eu-west-1/751354400372/evb-local) backend installed in your AWS account.
+*Note that the Step Functions flow will only happen when using `--replay-speed` > 0 or replaying from an OnFailure archive. Both require the [evb-local](https://serverlessrepo.aws.amazon.com/applications/eu-west-1/751354400372/evb-local) >= v0.0.8 backend installed in your AWS account.
 
 ## Caveats of paced and dead-letter replays
 Because the actual replay is targeting the Step Functions state machine and is actually dispatched back to the eventbus in the Dispatch step, the `replay-name` field is lost. This is due to limitattions in the SDK where you can't explicitly set it. Instead we're passing the replay ARN in the `resources` array.

evb-local-backend/src/step-functions/PacedCleanup.js

@@ -2,10 +2,9 @@ const AWS = require("aws-sdk");
 const eventbridge = new AWS.EventBridge();
 const lambda = new AWS.Lambda();
 const iam = new AWS.IAM();
-const eventBusName = "evb-cli-replaybus";
 exports.handler = async function (event, context) {
   for (const rule of event.Rules) {
-    const bus = rule.endsWith("dispatch") ? eventBusName : event.EventBusName;
+    const bus = event.EventBusName;
     const targets = await eventbridge
       .listTargetsByRule({
         EventBusName: bus,

evb-local-backend/template.yaml

@@ -14,7 +14,7 @@ Metadata:
       - evb-cli
       - debugging
     HomePageUrl: 'https://github.com/mhlabs/evb-cli#readme'
-    SemanticVersion: 0.0.7
+    SemanticVersion: 0.0.8
     SourceCodeUrl: 'https://github.com/mhlabs/evb-cli'
 Resources:
   OnConnectFunction:
@@ -353,8 +353,5 @@ Resources:
               - !Ref PacedReplayStateMachine
       Roles:
         - !Ref EventToStepFunctionsRole
-  ReplayBus:
-    Type: 'AWS::Events::EventBus'
-    Properties:
-      Name: evb-cli-replaybus
+
 Outputs: {}

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mhlabs/evb-cli",
-  "version": "1.1.26",
+  "version": "1.1.27",
   "description": "A package for building EventBridge/CloudWatch Events patterns",
   "main": "index.js",
   "scripts": {