A Database whose Irreversible Choices Are Made Deliberately

gcp-firestore

A Firestore database whose irreversible choices are made deliberately. Works with Terraform and OpenTofu (>= 1.6), google provider >= 6.0, < 7.0.

Three things here cannot be changed after creation: the database type (Native or Datastore mode), the location, and whether it uses your own encryption key. Getting any of them wrong means exporting every document into a new database and repointing every client, so permanent_choices is an output

• it belongs somewhere a person will read it before the next database is made.

delete_protection_state defaults to disabled. A terraform destroy, or simply removing the module, deletes the entire database. Firestore has no snapshots: point-in-time recovery is the only way back, it retains seven days at most, and it only helps if it was already on before the thing you want to recover from. There is no "restore from last night" unless you decided that last week.

deletion_policy is a Terraform-level setting, not a Firestore one. ABANDON leaves the real database in place when the resource leaves state, which is the right default for a database another application reads. DELETE plus no delete protection is two safeties off at once, and a precondition says so.

Smaller things: "(default)" is a real database name, not a placeholder, so the name validation accepts it specially; and concurrency_mode is surfaced because PESSIMISTIC holds locks for the length of a transaction, which only matters under contention and matters a lot there.

Verification

Static validation runs tofu fmt, init, validate, tflint and checkov. This module has not yet had a live test, so it is published as statically validated with its live test pending and does not carry the live-tested mark.