The Config That Got Everywhere
A single inherited config value silently shapes behavior in nine services, and no one remembers setting it. Echo wants to override it locally. Root makes her trace where the wind started — because you don't fix a draft by closing one window.
The wind leaves no mark and bends every tree. So does a default no one chose.
The bug was in nine services, and the cause was one environment variable nobody remembered setting.
Echo had traced it as far as the symptom: nine services, three teams, all rounding timestamps the same wrong way. "They don't even share code. There's no common library. How are nine unrelated things wrong in the exact same way?"
"Something's in the air they all breathe," Root said. "Find what they have in common that isn't code."
It was a variable. TZ_ROUNDING, set to a value none of the nine had asked for, inherited from a base container image, inherited in turn from a platform default someone had set — Echo finally found the commit — four years ago, 'temporarily,' to fix one report.
"One person set one default, once, to fix one thing," Echo said, "and it's been silently shaping every service built on that image ever since. None of them know it's there. It's not in any of their configs. It's just the wind they were born into."
"And now you want to override it in your service, locally, and move on."
"...Yeah. Fix mine, ship it."
"Close one window, in a house full of drafts." Root shook his head. "Your service gets better and the wind keeps blowing through the other eight, and the next person traces it for two days all over again. The gentle thing isn't weak. It's total — a default penetrates everywhere and leaves no mark, which is exactly why it's dangerous and exactly why nobody finds it. You don't fix a wind by stepping out of it. You go to the room it started in."
"The base image. I'd have to change the platform default. That's a much bigger ticket. That's other teams."
"That's the whole job. You found the secret recess the thing slinks in from. Now drag it into the light and put a name on it — make it a setting every service chooses on purpose, with a comment saying why, instead of a ghost they inherit and never see. A draft you can name is just air. A draft no one can find is what rots the house."
Configuration drift's quieter cousin: configuration defaults inherited through layers — a base image, a platform setting, a framework default — propagate invisibly into everything built on top, shaping behavior in services that never asked for them and don't list them anywhere. A single value set "temporarily" years ago can silently drive identical bugs across unrelated systems. Fixing it locally just leaves the draft blowing through everything else; the real fix is to trace it to its source and make the inherited ghost an explicit, named, commented choice.
Inspired by Configuration drift.
Penetration under the bed. Priests and magicians are used in great number. Good fortune. No blame. At times you must deal with hidden enemies, intangible influences that slink into dark corners and affect people by suggestion. Trace these things back to their most secret recesses. When such elusive influences are brought into the light and branded, they lose their power over people.
The figure. ䷸ The Gentle / the penetrating wind (Xùn), line 2 changing → ䷴ Gradual Progress (Jiàn). "Penetration under the bed... one deals with hidden enemies, intangible influences that slink into dark corners and affect people by suggestion. Trace these things back to their most secret recesses." Brought into the light and named, such elusive influences lose their power.
The reading. A default penetrates everywhere and leaves no mark — which is why nobody finds it and why it's dangerous. You don't fix a wind by stepping out of it; you go to the room it started in and give the ghost a name. A draft you can name is just air.
Department: IT (機)