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

@linzjs/cdk-tags

v1.7.0

Published

CDK construct to apply common tags to constructs

Downloads

2,701

Readme

@linzjs/cdk-tags

CDK construct to apply common tags to constructs

Usage

To apply the common set of tags for a s3 bucket:

import { applyTags, SecurityClassification } from '@linzjs/cdk-tags';

const bucket = new Bucket(this, 'ImageryArchive');

applyTags(bucket, {
  application: 'basemaps',
  group: 'li',
  classification: SecurityClassification.Unclassified,
  data: { isMaster: true, isPublic: true, role: 'archive' },
  criticality: 'low',
});

To apply the common set of tags for multiple constructs:

import { applyTags, SecurityClassification, TagsBase } from '@linzjs/cdk-tags';

const commonTags: TagsBase = {
  application: 'basemaps',
  group: 'li',
  classification: SecurityClassification.Unclassified,
  data: { isMaster: true, isPublic: true, role: 'archive' },
  criticality: 'low',
};

const bucket1 = new Bucket(this, 'ImageryArchive');
const bucket2 = new Bucket(this, 'AnotherImageryArchive');

applyTags(bucket1, commonTags);
applyTags(bucket2, commonTags);

Contributing

Responder Teams

Responder teams are used to route alerts to the correct team in OpsGenie. The responder team name must match the team name in OpsGenie. Only prod ops team members can create, rename or remove responder teams in OpsGenie.

Adding responder teams.

Contact the prod ops team in slack at #team-step-prod-ops to create a new team in OpsGenie. Once this team is created, add a new responder team to src/responder-teams.ts file with the new team name. These two names must match to ensure New Relic alerts are sent to the correct team.

Renaming responder teams.

Warning Consult the prodOps team regarding renaming a responder team. It is strongly recommended to never rename responder team names as this results in the teams having to apply the new responderTeam value to all their cdk stacks. When renaming a responder team, contact the prod ops team in slack at #team-step-prod-ops once the name as been updated, update src/responder-teams.ts to match the new name. And ensure you update the responderTeam in your applyTags() function across all stack the team owns.

Removing responder teams.

When removing a responder team, contact the prod ops team in slack at #team-step-prod-ops once the team has been removed, remove the team from src/responder-teams.ts file. And ensure you remove the responderTeam from your applyTags() function.