Features

Cross-cutting Pulumi capabilities that span multiple systems. These are user- or developer-visible features whose code touches the engine, multiple SDKs, and often the CLI surface.

Sub-pages

• Automation API — embedding Pulumi inside another program.
• Resource import — bringing existing cloud resources under management.
• State management — pulumi state and pulumi stack surgery.

Active contributors

Active contributors: Ian Wahbe, Thomas Gummerer, Justin Van Patten, Tom Harding, Fraser Waters

Why these are features, not systems

Each capability here is delivered by code in several places at once:

• Automation API lives in the SDK (sdk/{go,nodejs,python}/.../automation/), in the CLI (pkg/cmd/pulumi/operations/), and in the engine (custom programs as sources). To explain it, all three pieces have to be discussed together.
• Import has CLI, engine, and per-language-SDK code (the SDK exposes import as a resource option).
• State management spans CLI commands, the engine's pkg/resource/edit/, and backend interactions.

See also

• Systems index — the underlying building blocks these features compose.
• Apps: CLI — where every feature has a user-visible command.