Admin endpoints for dead-lettered messages

Open
  • Is something wrong?
#21 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
47/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, postgresql
Domain
backend-api-design, distributed-systems

Research direction

Start by reading the repository’s implementation of parked messages and its existing admin or message endpoints; the payload does not name specific files or tests. Work out how listing, retrying, and discarding should fit those patterns, then confirm each action works for dead-lettered messages.

Written by the indexing model from the issue text.

Description

enhancement

List, retry and discard parked messages.

Dominant language
C#
Stars
0
Forks
0
Avg merge
1h 4m
Merged PRs (30d)
8

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from softvasco/outbox-kit

All issues in softvasco/outbox-kit

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.