Pulumi rewards a little discipline. These are the practices that keep it maintainable as a team and a codebase grow.
The practices
- Keep programs declarative; push logic into tested helpers
- Use pulumi config set --secret for encrypted config
- Write unit tests with the language's normal test tools
What good looks like
An S3 bucket defined in TypeScript.
import * as aws from "@pulumi/aws";
const assets = new aws.s3.BucketV2("assets", {
bucket: "acme-assets",
tags: { Environment: "prod" },
});
export const bucketName = assets.bucket;Anti-patterns to retire
- Putting imperative logic with side effects in resource code
- Leaking secrets into stack config without encryption
- No unit tests despite using a real language
Want senior help putting Pulumi to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.