Configuration on Brian Faust

Test Cannot Prove Production When It Runs Different Rules

Sat, 01 Oct 2016 00:00:00 +0000

A label-layout change behaved correctly in test and disrupted document distribution in production. Both environments ran the same revision. The input looked equivalent. The test result was still incapable of predicting the production result.

The difference was deliberate. Test loaded one default and production loaded another. Users already had a way to select the layout they needed, but some had come to rely on the accidental production default. A new recommendation passed against the test rule while production continued through a different branch.

Runtime Configuration Is Process State

Sun, 01 May 2016 00:00:00 +0000

A queued job selected the settings for one business context by overwriting Laravel’s global configuration. The values were correct for that job. The problem was what happened afterward.

The worker stayed alive.

Only a small fraction of the queued job classes selected their context this way. A later job could read a key without first replacing it and inherit whatever the previous job had left behind. Nothing was wrong with the configuration file, environment variables, or deployment. The process contained valid values for the wrong work.