Old (cached?) config values appearing at runtime

[eob]

Steps to reproduce

First I try to update a config value:

firebase functions:config:set KEY=VAL1

Then I verify that it's updated

firebase functions:config:get KEY

Then I deploy

firebase deploy --only functions

But when I access the value at runtime (inside a firebase-function), I see the old value.

[rjhuijsman]

Just checking, does the closed issue mean that you found what was causing the behavior you saw? If yes, are you OK with sharing for posterity's sake? :)

[eob]

Yes -- sorry. User error. In order to run tests on my local machine, I have a wrapper around the firebase-functions library (because it causes problems when included on localhost). In production, the wrapper was incorrectly detecting that it wasn't running in GCS, and was loading the test values as a result instead of deferring to Google's notion of config.

…

Sent from my Tricorder

On Oct 27, 2017, at 3:20 PM, Robert-Jan Huijsman ***@***.***> wrote: Just checking, does the closed issue mean that you found what was causing the behavior you saw? If yes, are you OK with sharing for posterity's sake? :) — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.