Open stevejalim opened 1 week ago
@stevejalim FYI I've been cleaning up the switches to only keep the ones in use for #14092 — so after https://github.com/mozmeao/www-config/pull/582 this should be all — and only those used live will remain, not having to migrate junk.
Thanks @janbrasna - FYI @robhudson
Description
Now that we're using a centralised DB again, we can move our waffle-switch approach away from a separate repo (the
waffle_configs
directory inmomeao/www-config
and instead use the Django admin on the CMS deployment to manage them.The admin on the CMS deployment is connected to the primary DB, and waffle config changes will be flowed down to the replicas for the web pods effectively immediately, which will be faster than the current process, which reads from www-config a most every five minutes.
Whether we go (back?) to https://waffle.readthedocs.io/en/stable/ or use something else, we'll need to decide on an approach and also migrate existing switches from
www-config
into the Bedrock primary DB for Dev, Stage and Prod (as these all appear to have waffle configs inwww-config
.Success Criteria
www-config
'swaffle_configs
dir is migrated into the DBwww-config
is no longer read from as part of./bin/run-db-update.sh
waffle_configs
dir is removed fromwww-config