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

@ukautz/aws-cdk-envcontext

v0.6.2-beta1

Published

**This is an experiment** to increase ease-of-use of `cdk` within CI/CD.

Downloads

9

Readme

AWS CDK: Environment Context Experimental Feature

This is an experiment to increase ease-of-use of cdk within CI/CD.

What does it do?

TL;DR: You can export context into environment variables and they are automatically picked up the CDK execution.

Using the here provide App will make any environment variables with the prefix CDK_CONTEXT_ available in the context. The name in the context does not contain the prefix, e.g. from CDK_CONTEXT_someVar will be available with const someVar = this.node.tryGetContext("someVar"). The prefix can be modified in the AppProps.

Limitation: CDK internal context keys like "@aws-cdk/core:bootstrapQualifier" cannot be provided due to character limitations of environment variable names, which are: [a-zA-Z_][a-zA-Z0-9_]*. Could be solved with intermediate encoding, but seems like too much complexity in usage, for cases that could (and should?) be used via cdk.json or cdk.context.json and likely also better --context.

Use Case: CustomResources for CloudFormation that is implemented as Lambda and/or ECS task that executes cdk deploy, cdk destroy etc. Context parameters are provided by environment or secrets anyway.

Usage

Note: The created NPM package is hosted on Github packages as I do not consider it production ready and do not want to contribute to accidental installs… Read up how to use Github Packages hosted NPM packages if you want to use it.

in your bin/file.ts:

#!/usr/bin/env node
import 'source-map-support/register';
import * as cdk from '@aws-cdk/core';
import * as envcontext from '@ukautz/aws-cdk-envcontext';
import { YourStack } from '../lib/your-stack';

// use app from envcontext
const app = new envcontext.App();
new YourStack(app, 'YourStack');

Assuming the following environment variablse:

CDK_CONTEXT_myVar=foo
CDK_CONTEXT_otherVar=bar

Then in lib/your-stack.ts:

import * as cdk from 'aws-cdk-lib';
import { Construct } from 'constructs';

export class ExampleStack extends cdk.Stack {
  constructor(scope: Construct, id: string, props?: cdk.StackProps) {
    super(scope, id, props);

    // access context injected from env
    const myVar = this.node.tryGetContext('myVar');

    new cdk.CfnOutput(this, 'Vars', {
      value: `myVar = ${myVar}`, // will contain 'myVar = foo, someVar = bar'
    });
  }
}

Then in the command line:

$ export CDK_CONTEXT_myVar=foo
$ cdk synth

The rendered CloudFormation YAML should contain:

Outputs:
  Vars:
    Value: 'myVar = foo'

Using the context object

When working with a lot of parameterized values in context, here a little syntax sugar and simplified API to work with context.

import * as cdk from 'aws-cdk-lib';
import { Construct } from 'constructs';
import { contextOf } from '@ukautz/aws-cdk-envcontext';

export class ExampleStack extends cdk.Stack {
  constructor(scope: Construct, id: string, props?: cdk.StackProps) {
    super(scope, id, props);
    const context = contextOf(this);
    
    // get optional value, with fallback to default if missing
    const mayVar = context.may('myVar', 'saneDefault'); 

    // get mandatory value or throw exception if missing
    const mustVar = context.must('otherVar');

    // ...
  }
}

Useful commands

  • npm run build compile typescript to js
  • npm run watch watch for changes and compile
  • npm run test perform the jest unit tests