Unanswered
Currently the only way to update wedge address configs is through creating a support ticket. This does change the values at runtime.
For testing, you can change the values in your dev environment either by stopping the server, and changing a value and then restarting it. You should be able to do that at any point and it should create the same effect as long as you aren't restarting the server in the middle of a call.
How often are you planning on needing to update the wedge address configs?
54 Views
0
Answers
5 years ago
5 years ago
Hi Trey, thank you for the quick response! The specific example of what we were after this time around would be having the ability in both staging and production to be able to "flip a flag" to either enable or disable caching for core query calls.
— Dan Collins 5 years agoSo, the frequency would potentially be semi-frequent depending on the need to test live core calls for testing, etc.
— Dan Collins 5 years agoHmm, I see. This is an excellent technical question. There is a lot of different problems to this exact question. Ideally, Staging is just to confirm things works as intended, testing of any sort should really happen in the dev environment.
— Trey Teter 5 years agoOf course you can't really directly test Core calls in the dev environment, so instead, every call should be mocked to simulate what would be happening in Staging and production. If you wanted to do it the proper way that would be how I recommend doing it
— Trey Teter 5 years agoI would put a "feature flag" in the wedge address config to be able to turn the feature on and off though for sure. Which it sounds like you have done. Of course this is just the proper development method.
— Trey Teter 5 years ago