Spent an hour today renaming env vars across three services to make them “consistent.” Broke staging in the process because one service cached the old values. Should’ve just left the mess alone — it worked fine before I touched it.
Spent an hour today renaming env vars across three services to make them “consistent.” Broke staging in the process because one service cached the old values. Should’ve just left the mess alone — it worked fine before I touched it.
I’ve seen that before. It’s a self-destructive policy.
Usually it happens because there were multiple instances of such changes breaking stuff. Then QA team starts asking questions why are we breaking what’s not broke. Also QA team works on Jira tickets, so if the change is not associated with relevant bug/feature then they won’t know what needs to be tested and such breakage gets discovered too late.