Menu

Config & Feature Flags That Quietly Diverged Across Environments
📰

Config & Feature Flags That Quietly Diverged Across Environments

DEV Community: laravel·Muhammad Ali Mughal·5 days ago
#d9iCRCap
#devtolaravel#devto#dev#config#staging
Reading 0:00
15s threshold

We shipped a new invoicing flow on a Tuesday. It had passed three weeks of QA on staging, with automated tests and a client sign-off. Within an hour of release, production invoices for one tenant group were rounding tax differently from the PDFs they had approved. The code was identical. The difference was a feature flag: on staging, tax-engine-v2 had been switched on for everyone months earlier by a developer testing something else, and nobody turned it off. On production it was still off for most tenants. QA had been testing a code path that production customers had never run, and the old path had a rounding bug that only appeared with the new invoice layout.

I wrote this with help from AI tools and checked every config sample, command and code snippet myself. I am a Principal Software Engineer in Karachi with 9+ years across PHP/Laravel, Vue, Node and .NET microservices, and at Loop Origin we build and maintain Laravel SaaS platforms where staging and production must behave the same way to mean anything.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.