npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

overdrive

v0.0.3

Published

Redrive dead-letter messages back into an SQS queue.

Downloads

507

Readme

overdrive

Redrive messages from a dead-letter queue (DLQ) back onto an SQS queue.

Usage

$ overdrive -h
Usage: overdrive [options]

Redrive dead-letter messages back into an SQS queue.

Options:
  -V, --version          output the version number
  -q, --queue-url <url>  SQS queue url to redrive (required)
  -t, --timeout <ms>     time to wait for DLQ to empty (default: 60000)
  -h, --help             output usage information

A common way to run commands like this is to include it as an npm script in your service's package.json.

{
  "scripts": {
    "sqs:redrive": "overdrive --queue-url $MY_SQS_QUEUE_URL"
  }
}

Then execute it with npm sqs:redrive. You should see animated output similar to the following:

Redriving 295 messages...
progress: ⣀ [========================] 100%
Done.

How it works

  1. When you specify the main queue, overdrive will first query the queue attributes to parse the redrive-policy and obtain the DLQ url.

  2. Next it will drain the DLQ and push all of the dead-letter messages back onto the original queue.

  3. It ensures both the MessageBody and MessageAttributes are resent.

Requirements

When you do any work with SQS queues, you've got to have your AWS_REGION on hand, and that still applies here.

In addition, you'll need to get your IAM statements in order. Specific requirements will vary on your use-case, but assuming you've got one queue with a DLQ and both are encrypted with KMS, then your IAM statements should look something like this:

[{
  "Effect": "Allow",
  "Action": [
    "kms:Decrypt",
    "kms:GenerateDataKey"
  ],
  "Resource": "${kms_key.arn}"
}, {
  "Effect": "Allow",
  "Action": [
    "sqs:DeleteMessage",
    "sqs:GetQueueAttributes",
    "sqs:ReceiveMessage",
    "sqs:SendMessage"
  ],
  "Resource": "${queue.arn}"
}, {
  "Effect": "Allow",
  "Action": [
    "sqs:DeleteMessage",
    "sqs:GetQueueAttributes",
    "sqs:GetQueueUrl",
    "sqs:ReceiveMessage"
  ],
  "Resource": "${dead_letter_queue.arn}"
}]