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

grunt-aws-ecr

v0.1.3

Published

Grunt plugin for AWS's Elastic Container Repository service.

Downloads

2

Readme

grunt-aws-ecr

Grunt plugin for AWS's Elastic Container Repository service.

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-aws-ecr --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-aws-ecr');

The "aws_ecr" task

Overview

In your project's Gruntfile, add a section named aws_ecr to the data object passed into grunt.initConfig().

grunt.initConfig({
  aws_ecr: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
});

Options

Options configure the ECR service provided by aws-sdk. Valid options can be found in the AWS JavaScript SDK documentation. Not all options can be used with this plugin alone. Specifically sessionToken, credentials and credentialsProvider are unavailable with this plugin alone as they must be instances of classes provided by the AWS SDK not provided by this plugin.

A minimum working configuration for options would be:

{
  accessKeyId:     'STRING_VALUE',
  secretAccessKey: 'STRING_VALUE',
  region:          'us-west-2'
}

Command

Whether your configuration has a single task or multiple targets, each must inlude a command property. Commands are kebab case string in the style of the AWS cli (e.g. delete-repository, create-repository, etc.). CLI commands are all represented by methods in the SDK ECR service, except for get-login.

Params

Each command corresponds to a method in the SDK ECR service. Aside from command, noted above and callback, noted below, each property in a task's configuration is passed as a parameter to the SDK method. Valid parameters can be found in the documentation for the corresponding method. Methods have the same name as the corresponding command, but are in camel case.

Callback

Each command will receive the callback you provide in its configuration. The first and only argument will be the response from the AWS ECR service. This differs from SDK documentation.

Usage Examples

{
  command:    'get-authorization-token',
  callback:    data => console.log(JSON.stringify(data, null, 2)),
  registryIds: [ 'STRING_VALUE' ]
}

registryIds in this example is a valid AWS account number in which repository(ies) exist.

Release History

(Nothing yet)