73a9c34529
Twelve credential-driven env branches were routed through _enable_from_env on main (867e4158f0, #48820), which honors the loader's `_enabled_explicit` marker. The flag-driven WhatsApp step was the one survivor: `_whatsapp` still set `wa_cfg.enabled = True` on WHATSAPP_ENABLED=true regardless of an explicit YAML disable. The dashboard's disable action writes only `platforms.whatsapp.enabled: false` and leaves the env flag on disk, so the Baileys bridge reconnected to real contacts on the next full restart (reported live on #73289). Route the truthy branch through _enable_from_env like every other platform; WHATSAPP_ENABLED=false still forces a disable. Register the flag in _ENV_ENABLE_CREDENTIALS so the one-time explicit-disable WARNING can name it. Remaining scope of #96557 (the other ~20 sites) landed on main in867e4158f0and the config_env.py extraction; this is the delta. Fix direction from @CryptoDombili in #73303. Co-authored-by: Professor Dombili <Cryptodombili@gmail.com>
2 lines
14 B
Plaintext
2 lines
14 B
Plaintext
CryptoDombili
|