ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #pulumi
Pulumi stacks are isolated instances of your infrastructure program, not code copies. Learn how to use config files and Stack References to manage dev, staging, and prod without forking your code.
A decision guide for passing infrastructure outputs between Pulumi stacks, comparing Stack References with config, external secrets, and GitOps, plus a TypeScript implementation pattern.
Learn how to use Pulumi ComponentResource to encapsulate infrastructure patterns, enforce security boundaries, and eliminate configuration drift in large-scale IaC projects.
Stop copying VPC stacks between environments. Pulumi's Crosswalk for AWS lets you define a network once as a versioned component — with real trade-offs around NAT cost and abstraction limits.
Move Pulumi stack state into your own S3 bucket with versioning, least-privilege IAM, a verified locking story, and a tested export-based recovery path.
Learn how to embed Pulumi’s Automation API in a GitHub Actions workflow to provision an AWS S3 bucket automatically, with a concrete TypeScript example, safety gates, and a rundown of trade‑offs like state backend choice and debugging complexity.
Pulumi Component Resources let platform teams package organizational standards into typed, versioned, testable building blocks. Here's how they work, a working example, and when not to build one.
Pulumi component resources let you package repeated infrastructure patterns—like a VPC with subnets and routing—into one versioned, reusable unit. Here's how they work, with a TypeScript example and the trade-offs.
Learn how to encapsulate a VPC definition as a Pulumi Component Resource, instantiate it multiple times, and verify unique URNs and outputs without duplicating code.
typescript