pulumi-best-practices

Comprehensive best practices for writing reliable, maintainable Pulumi infrastructure code. Invoke this skill when: Why : Resources created inside apply() don't appear in pulumi preview , making changes unpredictable. Pulumi cannot properly track dependencies, leading to race conditions and deployment failures. Detection signals : Wrong : Right : When apply is appropriate : Reference : Why : Pulumi builds a directed acyclic graph (DAG) based on input/output relationships. Passing outputs directly ensures correct creation order. Unwrapping values manually breaks the dependency chain, causing resources to deploy in wrong order or reference values that don't exist yet. Detection signals : Wrong : Right : For string interpolation : Reference : Why : ComponentResource classes group related resources into reusable, logical units. Without components, your resource graph is flat, making it hard to understand which resources belong together, reuse patterns across stacks, or reason about your infrastructure at a higher level.