StoneFlyLabs.Reviver 1.0.5

Reviver

<p align="center"> <img src="assets/reviver_logo_pulse.svg" alt="Reviver logo" width="680"/> </p>

Interactive TUI for triaging and reprocessing Azure Service Bus dead-letter queues.

Reviver connects to an Azure Service Bus namespace, lists every queue and topic subscription that has dead-lettered messages, and lets you inspect, edit, and resend them — or seed a DLQ for load/failure testing.

Features

• Browse all queues and topic subscriptions with DLQ message counts in a single view
• Inspect message metadata, body (auto-formatted if JSON), and application properties
• Edit the message body in your $EDITOR before resending
• Add, edit, or remove application properties in-place
• Send to any queue or topic — with the choice to remove from DLQ or keep it there
• Automatic lock renewal every 25 seconds while you work so locks never expire mid-edit
• Seed a DLQ with synthetic messages for testing — usable from the TUI or as a headless CLI command
• Threshold-coloured DLQ counts: yellow (1–5), orange (6–20), red (21+)

Prerequisites

• .NET 10 SDK
• Azure CLI — run az login before starting; Reviver authenticates with your CLI credential

Installation

From NuGet

dotnet tool install -g StoneFlyLabs.Reviver

From source

git clone <repo>
cd Reviver
dotnet pack Reviver.Console/Reviver.Console.csproj -c Release
dotnet tool install -g StoneFlyLabs.Reviver --add-source Reviver.Console/nupkg

To update an existing installation:

dotnet tool update -g StoneFlyLabs.Reviver

To uninstall:

dotnet tool uninstall -g StoneFlyLabs.Reviver

Quick start

az login
reviver

You'll be prompted for a namespace name or FQDN. Short names are expanded automatically:

my-namespace  →  my-namespace.servicebus.windows.net

Usage

Interactive TUI

# Launch and prompt for namespace
reviver

# Pre-fill namespace, skip the prompt
reviver -n my-namespace

The TUI shows a table of all entities that have DLQ messages. Select one to receive a batch (up to 20), then pick a message to inspect. From the message detail screen you can:

Seed command (headless)

# Seed 50 messages into the "orders" queue DLQ
reviver seed orders -n my-namespace -c 50 -r "LoadTest"

# Seed into a topic subscription
reviver seed events/payments -n my-namespace -c 10

# Custom payload template
reviver seed orders -n my-namespace -p '{"id":"{guid}","seq":{index}}'

Payload template placeholders: {index}, {timestamp}, {guid}.

Version

reviver version

Configuration

Architecture

Two projects in one solution:

StoneFlyLabs.Reviver.sln
├── Reviver.Console/   — app (assembly: reviver)
│   ├── UI/App.cs      — all TUI screens and user interaction
│   ├── Commands/      — CliCommands (Cocona), SeederFlow (TUI seed wizard)
│   ├── Services/      — IServiceBusRepository, ServiceBusService, DlqSession
│   ├── Helpers/       — NamingHelper, PayloadTemplate, JsonHelper (pure, no Azure dep)
│   └── Models/        — EntityInfo, DlqMessage
└── Reviver.Tests/     — xUnit + NSubstitute unit/contract tests

App receives a Func<string, IServiceBusRepository> factory so the Azure layer is fully swappable in tests. DlqSession holds the ServiceBusReceiver that owns the batch lock — complete/abandon/renew all go through the same session object.

Development

# Build
dotnet build

# Run without installing
dotnet run --project Reviver.Console/Reviver.Console.csproj

# Run all tests
dotnet test

# Run a specific test class
dotnet test Reviver.Tests/Reviver.Tests.csproj --filter "FullyQualifiedName~NamingHelperTests"

# Pack
dotnet pack Reviver.Console/Reviver.Console.csproj -c Release

CI & Releases

Every push to main triggers a build, test run (results published as a GitHub Check), and a release.

Versioning defaults to bumping the patch component from the last tag (0.0.X). To cut a specific version, include it anywhere in the commit or PR body:

feat: redesigned entity list  v1.0.0

The release includes four self-contained binaries and the NuGet global tool package: