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

@adaliszk/pulumi

v3.52.4

Published

Pulumi configuration orchestration

Downloads

12

Readme

Simple Pulumi orchestration like any build-system

Idea

Normally, pulumi expects you to create a package that only contains deployment details. While this is a valid use-case, to integrate into development further you usually want to re-use that packages in a modular way. This is my take on this modular way, where I try to replicate the same concepts that most build-systems follow with a modular configuration and plugin ecosystem.

Provides

  • Everything from @pulumi/pulumi
  • @pulumi/kubernetes as k8s
  • @pulumi/random as random
  • Define Configuration method

Usage

  1. Install the package: yarn add -D @adaliszk/pulumi @pulumi/pulumi (pulumi is needed because the CLI expects it within the package.json)
  2. Create your configuration file pulumi.config.ts:
     import { defineConfig } from '@adaliszk/pulumi'
        
     export default defineConfig({
         createNamespace: true, // or use string for a specific name
         resources: [
             // List your resources that implements `Component`
         ]
     })
  3. Create Pulumi configuration file: Pulumi.yaml
     name: your-distribution
     description: >-
       An example pulumi distribution using @adaliszk configuration
        
     main: pulumi.config.ts
     runtime: nodejs
  4. Use the Pulumi CLI: pulumi up

Adding Resources

To define new resources for the system, you can build a project that exports out the appropriate function that implements the Component type. This wrapper function then needs to give back another that then have access to the deployment configuration such as the created namespace.

Example:

import {StackConfig, Component, ComponentDeployment} from '@adaliszk/pulumi'

export interface MyResourceOptions
{
    // Add your configuration 
}

export const myResource: Component = (options?: MyResourceOptions) => {
    return (config: StackConfig) => {
        // Create your resources
        // Return an object for exporting
    }
}

Ideally you should build this package, so that pulumi would need less compilation. For that, I recommend using tsup!

Versioning

Since this is a meta-package, the versioning reflect its main provided package, in this case @pulumi/pulumi. However, only the Major and Minor versions are kept in sync, and the Patch is used to bump the meta-package.