Change your components, keep your infrastructure

Pulumi’s experimental component state migrations feature enables component authors to upgrade or redesign reusable infrastructure components without replacing the cloud resources they already manage. Using an AWS VPC example, the text follows a network from the legacy AWSX VPC component to the modern AWSX version and finally to directly managed AWS resources, while preserving AWS resource IDs and dependencies such as an external security group. Because Pulumi state tracks resource URNs, component hierarchy, names, and parent relationships in addition to provider IDs, upgrades that reorganize resources require migrations beyond ordinary aliases. Migration callbacks transform old state records into new ones and define successor mappings so Pulumi can preserve dependencies and references across the stack. Authors can bundle, order, and retain migrations with their components, allowing users to skip intermediate versions and upgrade through normal preview and update workflows without manually editing state. Users should review previews for any remaining in-place provider changes, while component maintainers should test migrations and distribute them with component releases.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.