pulumi-infra

Name: pulumi-infra
Availability: InStock
Author: Esposter

Enforce Esposter Pulumi infrastructure conventions across packages and deployments.

23|3|Updated Jun 28, 2022

Search Tags:#devops #architecture #cloud #guidelines #infrastructure-as-code #pulumi #azure-native

Ready to run

npx skills add https://github.com/Esposter/Esposter --skill pulumi-infra-esposter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pulumi-infra
Source: https://github.com/Esposter/Esposter/tree/main/.agents/skills/pulumi-infra
Command: npx skills add https://github.com/Esposter/Esposter --skill pulumi-infra-esposter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Esposter relies on consistent Pulumi infrastructure practices across the monorepo to reduce deployment risk and maintainable code, but project-wide inconsistencies and manual migration steps create friction.

Core Features & Use Cases

Enforces per-file Azure resource declarations and a final one-resource-per-file rule to improve maintainability.
Maintains a ctix-generated barrel (src/index.ts) and generated outputs to ensure predictable deployments.
Provides import-migration guidance and architecture standards to streamline refactors and upgrades across packages/infra.

Quick Start

Apply these conventions whenever editing packages/infra to ensure a consistent, safe Pulumi deployment.

Frequently Asked Questions about pulumi-infra

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce consistent naming and structure in Pulumi infrastructure code?▼

To enforce consistent Pulumi infrastructure practices, you can apply conventions that dictate a strict file structure and per-file resource declarations. This ensures predictable deployments and reduces project-wide inconsistencies.

Why does my Pulumi build fail when multiple Azure resources are declared in one file?▼

Pulumi builds may fail if the one-resource-per-file rule is violated. Enforcing per-file Azure resource declarations improves maintainability and ensures compatibility with generated outputs and safe deployment workflows.

What is the best way to manage generated barrel files for Pulumi deployments?▼

The best way to manage generated barrel files is to maintain a ctix-generated index.ts. This ensures predictable deployments by standardizing the project structure and handling generated outputs safely across packages.

Do I need migration guidelines when refactoring Azure-native infrastructure as code?▼

Yes, you need import-migration guidance and architecture standards when refactoring Azure-native infrastructure as code. These guidelines streamline package upgrades and ensure safe, compatible Pulumi deployments.

How does standardizing Pulumi project structure reduce deployment risk in a monorepo?▼

Standardizing Pulumi project structure reduces deployment risk by enforcing predictable build, preview, and deployment workflows. This maintains consistent resource naming and architecture standards across the monorepo.