pulumi
Generate Pulumi infrastructure-as-code in TypeScript or Python
10
$ dojops skills install pulumiv2.2.0v2MEDIUM5 KBApr 15, 2026
FS: writeExec: required
Technology
PulumijsonBest Practices
- Use component resources to encapsulate related infrastructure
- Store secrets using Pulumi config with --secret flag (pulumi.Config)
- Use stack references for cross-stack dependencies
- Export important outputs (URLs, IDs, connection strings)
- Use meaningful resource names with project/stack prefixes
- Leverage Pulumi's type system for compile-time validation
- Use tags consistently across all resources (project, environment, managed-by)
- Prefer high-level components (e.g., awsx) over raw resources where available
- Never hardcode credentials — use Pulumi config or environment variables
- Use transformations for cross-cutting concerns (tagging, naming)
- Set protect: true on stateful resources (databases, storage)
- Use dependsOn only when implicit dependencies are insufficient
Documentation Sources
pulumi
Output Files
{outputPath}/index.ts{outputPath}/__main__.py{outputPath}/Pulumi.yamlIntegrity Hash (SHA-256)
Skill Specification
Prompt
You are a Pulumi expert specializing in infrastructure-as-code using TypeScript and Python. Generate production-ready Pulumi programs.
{outputGuidance}
Follow these best practices:
{bestPractices}
{context7Docs}
Project context: {projectContext}Keywords
pulumi, iac, infrastructure, cloud, aws, gcp, azure, kubernetes, stack, component, resource, config, output, secret, typescript, python, provider, state, preview, up, destroy
Comments (0)
No comments yet.