AdminAsOneOffProcesses [rule] v1.0.0

DB migrations, console sessions (REPL into prod data), one-off scripts (scripts/import.js) — all run as one-off processes against an identical release of the same codebase. They use the same env, the same dependencies, the same code. They do not run from a developer's laptop with snapshot data.

Checks

• Migrations run via release run rake db:migrate (or platform equivalent), against the deployed release.
• Console / REPL is a one-off process attached to a release, not a local script with prod credentials in env.
• Admin scripts ship in the same repo and are invoked through the same build pipeline.
• The same release ID handles web, worker, and admin invocations.

Label

Run admin / management tasks as one-off processes

AdminAsOneOffProcesses [rule] v1.0.0

DB migrations, console sessions (REPL into prod data), one-off scripts (scripts/import.js) — all run as one-off processes against an identical release of the same codebase. They use the same env, the same dependencies, the same code. They do not run from a developer's laptop with snapshot data.

Checks

• Migrations run via release run rake db:migrate (or platform equivalent), against the deployed release.
• Console / REPL is a one-off process attached to a release, not a local script with prod credentials in env.
• Admin scripts ship in the same repo and are invoked through the same build pipeline.
• The same release ID handles web, worker, and admin invocations.

Label

Run admin / management tasks as one-off processes

Relations

requires: [@backend-architecture/principle-build-release-run]

Label

Run admin / management tasks as one-off processes

Requires

• @backend-architecture/principle-build-release-run