terraform.tfstate or a Pulumi checkpoint, under one lock
plungefor Pulumi
+
+ A marker on the resource itself, written by the create call.
+ + + plunge-stack = payments/prod + plunge-urn = …Bucket::receipts +The same, keyed by stack and URN. Labels carry a digest.
+ + + + +A record per resource holds only what a read leaves out, such as a generated password. The state file stays on as a cache you can delete.
+ + + +A record per resource holds its full state, secrets as ciphertext. There is no checkpoint to keep.
+ + + + +No lock. Each record write is conditional, so applies on different resources both land and a clash is refused by name.
+ + + +No stack lock. Updates on different resources both land, and a stale saved plan is refused naming the record that moved.
+ + +The list inside the state file. Only the tool holding it can say what is owned.
terraform.tfstate or a Pulumi checkpoint, under one lockterraform.tfstate or a Pulumi checkpoint, one lock
plungefor Pulumi
- A marker on the resource itself, written by the create call.
+A marker on the resource, written at create.
plunge-stack = payments/prod plunge-urn = …Bucket::receipts -The same, keyed by stack and URN. Labels carry a digest.
+Keyed by stack and URN, as a digest on labels.
-A record per resource holds only what a read leaves out, such as a generated password. The state file stays on as a cache you can delete.
+A record per resource for generated values. The state file becomes a local cache.
-A record per resource holds its full state, secrets as ciphertext. There is no checkpoint to keep.
+A record per resource with its full state, secrets encrypted.
-No lock. Each record write is conditional, so applies on different resources both land and a clash is refused by name.
+A conditional write per record. Applies on different resources land together.
-No stack lock. Updates on different resources both land, and a stale saved plan is refused naming the record that moved.
+A conditional write per record. Updates on different resources land together.
-The list inside the state file. Only the tool holding it can say what is owned.
The resource list inside the state file.
A record per resource for generated values. The state file becomes a local cache.
+A record per resource for generated values.
diff --git a/src/content/docs/compare/state-file.mdx b/src/content/docs/compare/state-file.mdx index 880c92f..a49ecc5 100644 --- a/src/content/docs/compare/state-file.mdx +++ b/src/content/docs/compare/state-file.mdx @@ -2,15 +2,20 @@ title: "choudoufu, plunge and the state file" wide: true tableOfContents: false -description: "A state file holds identity, values and writes in one file under one lock. choudoufu for OpenTofu and plunge for Pulumi split them, and an estate becomes whatever carries its label." +description: "Terraform and Pulumi set state boundaries with a lock. choudoufu for OpenTofu and plunge for Pulumi let the resources draw them, with a record and a conditional write per resource." --- import Arenas from '../../../components/Arenas.astro'; +import Boundaries from '../../../components/Boundaries.astro'; import StateCells from '../../../components/StateCells.astro'; import * as cdf from '../../../data/compare-choudoufu-state.mjs'; import * as pl from '../../../data/compare-plunge-state.mjs'; -A Terraform state file and a Pulumi checkpoint do three jobs in one file. They map each address to a live object, hold generated values, and order writes. One lock covers all of it. [choudoufu](https://intentius.io/choudoufu/) and [plunge](https://intentius.io/plunge/) split those jobs apart and run your configuration and programs as they are. +Terraform and Pulumi each sew identity, values and writes into one file behind one lock, and that lock sets the state boundary. [choudoufu](https://intentius.io/choudoufu/) and [plunge](https://intentius.io/plunge/) unravel both. The resources' own labels draw the estates, and the storage service's conditional writes handle two runs at once. + +Terraform and PulumiThe lock draws the boundary
-choudoufu and plungeThe resources draw the boundary
-Each resource carries its estate's label, and the labels draw the estates. Every record has its own lock: the storage service's conditional write.
+One record store serves every account. The labels draw the estates, across accounts when a resource is named in your code, and every record has its own lock: the storage service's conditional write.
Terraform and PulumiThe lock draws the boundary
-Lock as boundary
+Each state file sews identity, values and writes together behind one lock, in Terraform and Pulumi alike. A state boundary is whatever that lock covers.
+One state file, one lock. Whatever the lock covers is one boundary.
choudoufu and plungeThe resources draw the boundary
-Labels as boundary
+One record store serves every account. The labels draw the estates, across accounts when a resource is named in your code, and every record has its own lock: the storage service's conditional write.
+Each resource carries a label. Resources with the same label are one estate, in any account.
Lock as boundary
-Estate boundaries as application locks
+One state file, one lock. Whatever the lock covers is one boundary.
+The tool keeps an estate in one state file behind its own lock. Whatever that lock covers is the estate.
Labels as boundary
-Estate boundaries as resource labels
+Each resource carries a label. Resources with the same label are one estate, in any account.
+Each resource carries a label, and resources with the same label are one estate, in any account. Each gets its own record, guarded by the storage service's native lock.
Estate boundaries as application locks
-The tool keeps an estate in one state file behind its own lock. Whatever that lock covers is the estate.
+An estate is one state file behind the tool's own lock. Apply 2 waits for apply 1, though they touch different resources.
Estate boundaries as resource labels
-Each resource carries a label, and resources with the same label are one estate, in any account. Each gets its own record, guarded by the storage service's native lock.
+Resources with the same label are one estate, in any account. Each resource has its own record and lock, so apply 1 and apply 2 run together.
{description}
} +{lead && description &&{description}
} {wide && } diff --git a/src/components/Landing.astro b/src/components/Landing.astro index 10263fc..1ac883f 100644 --- a/src/components/Landing.astro +++ b/src/components/Landing.astro @@ -16,7 +16,7 @@ const { part = 'top' } = Astro.props; // One row of cards under the header, each straight into a page of the site. const cards = [ { title: 'Comparing Intentius to the rest', body: "Free, against each vendor's top tier.", href: '/compare/terraform-platforms/' }, - { title: 'State locking', body: 'Application locks or resource labels, for OpenTofu and Pulumi.', href: '/compare/state-locking/' }, + { title: 'Coordinating changes', body: 'Application locks or resource labels, for OpenTofu and Pulumi.', href: '/compare/coordinating-changes/' }, { title: 'Move off another runner', body: 'Atlantis, Terraform Cloud or Spacelift, one repo at a time.', href: '/for/moving/' }, { title: 'Carve up a large estate', body: 'Hundreds of roots, or one state file shared by too many teams.', href: '/for/estate/' }, ]; diff --git a/src/components/StateCells.astro b/src/components/StateCells.astro deleted file mode 100644 index ba753f9..0000000 --- a/src/components/StateCells.astro +++ /dev/null @@ -1,197 +0,0 @@ ---- -// The state model as cells. Rows are the three jobs a state file does -// (identity, values, writes) and a fourth for the estate. The stock column -// is one tall cell, one file under one lock; choudoufu and plunge each give -// every job its own cell; the estate row joins the two into one cell, an -// estate named by a label on the resources. Pure HTML and CSS, so it reads -// without script and in both themes. -const C = 'https://intentius.io/choudoufu'; -const P = 'https://intentius.io/plunge'; ---- -terraform.tfstate or a Pulumi checkpoint, one lock
plungefor Pulumi
-
- A marker on the resource, written at create.
- - - plunge-stack = payments/prod - plunge-urn = …Bucket::receipts -Keyed by stack and URN, as a digest on labels.
- - - - -A record per resource for generated values.
- - - -A record per resource with its full state, secrets encrypted.
- - - - -A conditional write per record. Applies on different resources land together.
- - - -A conditional write per record. Updates on different resources land together.
- - -The resource list inside the state file.
{title}
} +{title}
} + {intro &&{intro}
}