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

loopback-connector-firehose

v1.1.0

Published

Loopback.js connector for Amazon Kinesis Firehose

Downloads

5

Readme

loopback-connector-firehose

Loopback connector for AWS Kinesis Firehose

Usage

First make sure that you have AWS credentials in .aws/credentials file.

Next, make sure that in your datasources.json the something like the following exists:

  "firehose": {
    "name": "firehose",
    "connector": "loopback-connector-firehose",
    "region": "us-west-1",
    "DeliveryStreamName": "delivery-stream-name",
    "ColumnNames": ["messageId","stringData"]
  }

Where ColumnNames is the RedShift column name for which your delivery stream has been constructed.

This connector is a non-database connector, which means that standard API representing CRUD operations does not get created by default. Instead it binds the send remoting method to the model.

The data that gets sent to it will be formed into pipe delimited string, which will then be sent out.

If data being passed into the connector includes DeliveryStreamName, the connector will use that instead of settings defined one. This is recommended when you have many different delivery streams for a given abstract model defined route.

To use dynamic delivery stream, make sure your abstract model has remoting hook that sets the delivery stream name before remoting:


  MyModel.beforeRemoting( 'send', function( ctx, modelInst, next) {
    ctx.args.data.DeliveryStreamName = "delivery-stream-name";
    next();
  });