Config, secrets, and code

Saturday morning, and the most important change of race week is a pull request that builds no feature. It builds Sunday.

The same container image runs in staging and production and behaves differently in each, and the difference arrives from outside the box. A running process is handed named values as it wakes, each an environment variableConcept · lights on your mapenvironment variableA named value supplied to a process when it starts, which database, what log level, keeping environment-specific values outside the code and changeable without rebuilding.: which database to talk to, which feature flags to read, how loudly to log. The whole collection of such settings is the system’s configurationConcept · lights on your mapconfigurationThe settings controlling how software behaves in a particular environment. Code defines what the application can do; configuration decides how it operates here., and the split is the part to remember: code decides what the software can do, configuration decides how it behaves here. One image, four worlds, four configurations. That is how the ladder from Act II actually works.

The values that grant power

Some configuration is dangerous to know. Database passwords, Ledgerline’s API keys, signing keys: each is a secretConcept · lights on your mapsecretSensitive configuration that grants power: passwords, keys, credentials. Never embedded in source or images, since code gets copied and history remembers forever. All secrets are configuration; most configuration is not secret., and the iron rule is that secrets never live in source code, since repositories remember everything forever and get cloned onto laptops that get left on trains. Instead each box, as it wakes, asks a secrets managerConcept · lights on your mapsecrets managerA service storing sensitive values encrypted, checking the asker’s identity, logging every access, supporting rotation and revocation. The application fetches the secret at runtime instead of carrying it. for what it needs: identity checked, access logged, values rotatable overnight without touching code. The Act IV audit will walk this exact corridor with a clipboard, and race week is why the corridor will pass.

Sunday, described in files

And the pull request itself? It describes machines. Thirty tracking machines from 5 a.m., doubled projection headroom, the scale-up rules, the alarms: all of it written as infrastructure as codeConcept · lights on your mapinfrastructure as codeDefining infrastructure, machines, networks, scaling rules, permissions, in machine-readable files a tool applies. Reviewed, versioned, repeatable: the structure can be rebuilt from its description. It rebuilds structure, not data., files in the repository that a tool reads and makes true. Nobody will hand-build a server tonight. Sam wrote Sunday down, Priya reviewed Sunday like any other diff, and the pipeline will conjure Sunday from its description before first light. The infrastructure got the full Act II treatment, commits and review and history. It is code now. That is the sentence the whole scene is for.

The machines are described, the secrets are locked, the freeze holds. Saturday afternoon belongs to the last quiet thing before the noise: reading the whole architecture, wall to wall, at last.