declarative-infra ยท diff

git:20261024.f18ae25 to git:20261107.b47c639

1 added, 1 removed. Audit A to A.

What this update changes in the checks

No check changed: every fixed check gives the same answer before and after this update.

A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.

---
name: declarative-infra
- description: Use when changing NixOS, OpenTofu, cloud resources, infrastructure secrets, deployments, or provider credentials, even when another repository owns them. Routes changes through the owning repository and trusted deployment path.
+ description: Use when changing NixOS, OpenTofu, cloud resources, infrastructure secrets, deployments, or provider credentials, even when another repository owns them.
---
# Declarative infrastructure
## Ownership and mutation
Each host's infrastructure has exactly one home: the `infra/` directory of the repository it serves, or a dedicated infrastructure repository. Everything for that host changes in that home, even when the work starts in another repository.
Live state changes only through the home's reviewed main-branch automation, so production always matches a reviewed commit. Running `deploy-rs`, `tofu apply`, or `nixos-rebuild switch` by hand is an emergency measure. If you do it, say so in your report.
## Changing existing infrastructure
Keep OpenTofu `moved` and `import` blocks in the repository after they apply, as the record of what happened. A migration or refactor is ready to merge only when its plan is a no-op.
Data-bearing resources carry `prevent_destroy`, so deleting one takes two changes: the first lifts the guard, the second destroys the resource.
## Validation
Before pushing, run `nix flake check`, build each host's toplevel, run `tofu fmt -check`, and run `tofu init -backend=false && tofu validate`. Where credentials are available, also produce a plan.
## References
| Change | Reference |
| --- | --- |
| A new infrastructure home, host layout, PostgreSQL, Nix caching, private registry access, or host deployment | [Bootstrapping a host repo](references/bootstrap.md) |
| SOPS identities and recipients, CI secrets, or brokered provider credentials | [Secrets bootstrap](references/secrets.md) |
| Preview environments | [Pull request previews](references/pr-previews.md) |
| Releasing, rolling back, or hosting a first-party app's container images | [App releases](references/app-release.md) |
| Third-party container updates whose publisher the infrastructure owner doesn't control | [Vendor image updates](references/vendor-images.md) |
Web hosts get pull request previews by default. Leaving them out takes a decision recorded in the host repository.
Development environment layers and where each value is documented belong to the secrets-and-config skill.