Skip to content
plungeDocs

Adopt a Pulumi stack

llms.txtlists every page for an agent

Who it is for

You run Pulumi today, on a DIY backend (a directory, S3, GCS or Azure Blob) or on Pulumi Cloud.

Features

  • plunge stack adopt --json classifies your checkpoint and writes nothing
  • Adoption keeps every ID and gives each resource its own record
  • Adopting the same checkpoint again does nothing
  • A stock pulumi stack export from Pulumi Cloud gives the file plunge stack adopt --file takes
  • Keep the hosted backend for the stacks it runs today, and try one exported stack first

Differences from stock Pulumi

  • A plunge+ backend URL, and two marker tags on each resource.
  • Unnamed resources get a fixed name in place of a random suffix.
  • Deletes check the markers first.
  • No stack history; bucket versioning keeps each record's versions.
  • Your hosted stacks stay where they are until you adopt one. Issue #8 lists each Pulumi Cloud feature and how chant works next to it.

First step

Adopt an existing stack

Then read

How-to
Adopt an existing stackSet up by handRun it from CI
Explanation
OverviewRecords
Reference
The adopt documentPulumi Cloud features and chant (#8)Commands, URLs and variables

plunge