+ jHjHaR/t-0tRt^RIt^RIt^RIHt^RIHtHtH t H t H t H t H t ^RIHtHtHt^RIHt]P(!R4t] t]!4t]^k] P2R0/t]^kRRltR R ltR R ltR RRR/RRlltRRltRRlt RRlt!RRlt"RRlt#RRlt$RR lt%R!R"lt&R#R$lt'R%R&lt(R'R(lt)R)R*lt*R+R,lt+R-R.lt,R#)1uEnvironment-variable overrides for the gateway config (``_apply_env_overrides``). Runs after ``GatewayConfig.from_dict`` so env always wins over config.yaml / gateway.json. Most platforms follow one shape — "credentials present in env ⇒ enable the platform and copy the values into ``extra``" — declared by each platform plugin as ``PlatformEntry.env_overrides`` (``gateway.platform_env.EnvCred`` rows; see that module). Core-only platforms (api_server, webhook, msgraph_webhook, relay) keep their small functions here. N)Optional) GatewayConfig HomeChannelPlatformPlatformConfig _getenv_str_has_usable_api_server_key SHARED_LISTENER_MIRROR_PLATFORMS)INT csv_extras env_extras)is_truthy_valuezgateway.configc0V^8dQhR\R\/#)platformreturn)rtuple)formats"7/home/ubuntu/.hermes/hermes-agent/gateway/config_env.py __annotate__r*s  x E cV\9d\V,#^RIHpVPVP4p\ \ VRR4;'gR4pV'g*^RIHpV!VP4;'gR^,pV#)zWARNING credential names: the core row, else the platform entry's declaration. The entry is already materialized (its own env step is what is warning), so the lookup never imports.platform_registryenv_enable_credentials)bundled_env_rows)rr) _ENV_ENABLE_CREDENTIALSgateway.platform_registryrgetvaluergetattrgateway.platform_envr)rrentrynamesrs& r_enable_credential_namesr%*sq**&x00;  ! !(.. 1E '%!92>DD" EE 9!(..1==XqA Lrc(V^8dQhR\RR/#)rrrN)r)rs"rrr8sxDrcV\9dR#\PV4\V4pVUu.uFDp\PP V4;'gRP 4'gKBVNKF ppRPT;'gT4;'gRp\PRVPVPW@P4R#uupi)zOne-time WARNING: ``platforms..enabled: false`` wins over env creds (which used to force-enable), so users relying on "creds in .env = on" learn why it went dark.Nz, zits credentialsa%Platform '%s' is explicitly disabled by platforms.%s.enabled: false in config.yaml, so the credentials found in the environment (%s) will NOT start its adapter. Environment credentials no longer override an explicit disable. Remove the key or set platforms.%s.enabled: true to turn it back on.) _EXPLICIT_DISABLE_WARNEDaddr%osenvironrstripjoinloggerwarningr )rr$npresentcredss& r _warn_explicit_disable_beats_envr48s++  * $X .EE%QBJJNN1$5$;$;#B#B#Dqq%GE IIg&& ' < <+ d d13 d d8Mh8W[d8ddr pop_markerFwarnTc TV^8dQhR\R\R\R\R\/#)rconfigrrArBr)rrr7r)rs"rrrTs4 %->BRVrcxVPPV\44pVPpV'dVP RR4MVP RR4pVP 'dV#V'g/VP\9d\4'g RVnV#V'd \V4V#)aEnable *platform* on env credentials unless config.yaml explicitly disabled it. A multiplex secondary profile may pin ``enabled: false`` yet inherit the process env; without this guard env presence would force-enable it. By default the ``_enabled_explicit`` marker is READ (the plugin-enable and relay passes still need it) and the disable is warned once; api_server/webhook POP it (terminal branch) and stay silent. _enabled_explicitFT) platforms setdefaultrextrapoprenabledr r r@r4)rDrrArBplatform_configrIexplicits&&$$ r_enable_from_envrNTs&&11(N?@G89L;``env_enablement_fn()`` result as a non-empty dict, else None.Nz#env_enablement_fn for %s raised: %s)env_enablement_fn Exceptionr/debugname isinstancerz)r#seedes& r_plugin_probe_seedrsi &&&(dD))d4<<  :EJJJsA A;!A66A;cRV^8dQhR\R\\,R\/#)rexisting_extrarr)rzrr7)rs"rrrs&Xd^PTrc T;'g/P4Fwr4VR8wgKVPW44K! \VP\ RVR744pT'g!\ PRTP4T# \ d-p\ PRTPT4Rp?R#Rp?ii;i)zk``entry.is_connected`` on a transient ``enabled=True`` view seeded with env extras (never the real config). home_channelT)rKrIu6is_connected for %s raised: %s — skipping enablementNFucPlugin platform '%s' available but not configured (is_connected returned False) — skipping enable) itemsrHr7 is_connectedrr}r/r~r)r#rrkv configuredexcs&&& r_plugin_is_configuredrsZZR&&(DAN"))!/)%,,^DP^-_`a    @ JJ   Muzz[^_s!BB:B C!CCc(V^8dQhR\RR/#rPrQ)rs"rrrs**M*T*rc \VP4pTP P T4pTRJ;'d TPpTe \TP;'g/4M/pTe#T'gTP RR4'dR#\T4pT'g#TPe\YT4'gR#\TP44pT'gTPfR#TP P!T\#44p RT nT'd\T4pTP%RR4p T PP'T4\)T \4'dT P R4'dr\+T\-T R,4\-T P R4;'gR 4T P R 4'd\-T R ,4MRR 7T nR#R#R#R# \d-p\P RTPT4Rp?R#Rp?ii;i \d/p\P RTPT4RpRp?ELRp?ii;i) zunknown platform name %r: %sNrFFzcheck_fn for %s raised: %sTrchat_idrHome thread_id)rrrr)rrr}r/r~rGrrKrzrIrrrr7check_fnensure_deps_fnrHrrJupdaterrstrr) rDr#rr existing_cfgalready_enabledrrdeps_okrLhomes && r_enable_plugin_platformrsEJJ'##''1L"$.GG<3G3GO7C7OT,,,223UWNN#I99I>c0V^8dQhR\R\/#)rrDrrlist)rs"rrrs  }  rc^RIHpV!4^RIHp^RIHpV!V/VP R7# \d#p\PRT4.uRp?#Rp?ii;i)ugPlugin entries with activation evidence (config block, env/.env, credential pool); only those are imported — an unconfigured adapter has nothing to enable. See gateway.platform_activation. config.yaml blocks already materialized their adapters in load_yaml_layer (and every merged block is in config.platforms), so the YAML is not parsed a second time here.)discover_pluginsr)configured_plugin_entriesyaml_cfgplatform_namesz6Plugin platform discovery for env overrides failed: %sN) hermes_cli.pluginsrrrgateway.platform_activationrrGr}r/r~)rDrrrrs& r_configured_plugin_entriesrsQ 7?I():RX^XhXhii  MqQ s-0 AAAAc<V^8dQhR\R\R\/#)rrDentriesrr)rs"rrrs!=4Drc ^RIHp^RIHp^RIHpHpVUu0uFp\VRR4kK pp\\P!4^,4\V4,V, pV'g.#V!/VPR7p .p \V4F]p V !V 4'd V!V 4MRp V 'gK%V ^,'gK6V PV!W^,V ^,R74K_ V #uupi) aEnv rows of bundled platforms with activation evidence but no registry entry (discovery suppressed or the plugin disabled), read from their ``gateway_env`` files; see ``gateway.platform_env.bundled_env_rows``. They only run the env steps, never the enable pass.)SimpleNamespace)activation_predicate)_BUNDLED_ENV_SIBLINGSrrr(rN)r env_overridesr)typesrrrr"rrr!setr_scan_bundled_plugin_platformsrGsortedappend) rDrrrrrrhaver$wantedoutrrowss && r_bundled_env_fallbacksrs&@L,3 4GqGAvr "GD 4 88:1= >EZA[ [_c cE  !2f>N>N OF Cu )/%4 4DGG JJDQ`def`gh i J 5sC;c$V^8dQhR\/#r6)int)rs"rrrsSrc\\PP44pVP \VP 44# \ \3d\T4u#i;i)N) rr __members__valuesindexr ValueErrorKeyErrorlen)r#memberss& r_platform_rankrsX8''..01G}}Xejj122  !7|s#A A,+A,c4V^8dQhR\R\RR/#rrDrrNr)rs"rrrs& N N N N Nrc\V\R7F*p\VRR4;'gRF pV!V4K K, R# \d-p\P RTP T4Rp?KHRp?ii;i)aRun each plugin platform's declared ``env_overrides`` steps (credential enable, home channel, reply mode, ...). Every step touches only its own platform, so only the order WITHIN an entry is significant (e.g. Telegram's reply mode may create the entry its home channel then attaches to).)rUrzenv override for %s raised: %sNr)rrr!r}r/r~r)rDrr#steprs&& r_apply_plugin_env_overridesrsl^4E?B7==2=D NV >5 N =uzz1MM NsA A9 !A44A9c4V^8dQhR\R\RR/#rr)rs"rrrs& Y Ym Yd Yt YrcVFp\W4K R# \d-p\PRTPT4Rp?KGRp?ii;i)uRegistry-driven enable for plugin platforms whose ``env_overrides`` did not already enable them. Enabled when credentials are configured (``is_connected`` MUST gate: ``check_fn`` alone would enable unconfigured platforms that retry-connect forever) and deps are present (``check_fn``) or installable later by ``create_adapter()`` — never here: installing in this sweep boot-looped the app. z-Plugin platform enable pass failed for %s: %sN)rr}r/r~r)rDrr#rs&& r!_enable_plugin_platforms_from_envrsI Y #F 2 Y LLH%**VW X X Ys  A!A  Ac(V^8dQhR\RR/#rPrQ)rs"rrr,s,(,(=,(T,(rc\R4P4pVPP\P 4pV'd=\ VPPR4;'gR4P4MRpT;'gTpV'dM\V\P 4pVPR4VPR&VP'gR#V'd\\R44'dR#\P \P\P\P0pVPP4FwrxWv9gVP'gKVPPR4'd"\ P#RVP$4M \ P'R VP$4R Vn K R#) uRelay (connector-fronted, EXPERIMENTAL): enabled by GATEWAY_RELAY_URL or gateway.relay_url; the URL is mirrored into extra["relay_url"] for the connected-checker. Relay-exclusive: the GATEWAY_RELAY_URL env stamp means the connector owns every platform connection; a directly-connected adapter would be a second unmanaged ingress (duplicate deliveries, split sessions, a socket disarming scale-to-zero). So the env stamp disables all other messaging platforms — even explicitly enabled ones — except non-messaging surfaces (local, api_server, webhook; same set as the scale-to-zero arm gate). relay_url from YAML only keeps the additive behavior. Opt out with GATEWAY_RELAY_ALLOW_DIRECT_PLATFORMS=true. GATEWAY_RELAY_URL relay_urlr(/N$GATEWAY_RELAY_ALLOW_DIRECT_PLATFORMSrFa>Relay connector is configured via GATEWAY_RELAY_URL; disabling directly-connected platform '%s' even though it is explicitly enabled in this profile's configuration. All messaging goes through the connector on this deployment. Set GATEWAY_RELAY_ALLOW_DIRECT_PLATFORMS=true to keep direct platforms alongside the relay.z`Relay connector is configured via GATEWAY_RELAY_URL; disabling directly-connected platform '%s'.F)r^r-rGrrRELAYrrIrNrstriprKr LOCALr_rgrr/r0r info) rD relay_url_envexisting_relayrelay_url_yaml relay_url_val relay_configskiprrLs & r_relayr,sl./557M%%))(..9NQ_S--11+>DD"EKKMegN!33^M'? *7*>*>s*C ;'###  OF3Y,Z[[ NNHNNH,?,?AQAQ RD%+%5%5%;%;%=!  ?#:#:#:   $ $%8 9 9 NN@   KK>  #('&>rc(V^8dQhR\RR/#rPrQ)rs"rrr[s==M=d=rcVPP4FpVPPRR4K! R#)rFN)rGrrIrJ)rDrLs& r_scrub_explicit_markersr[s2!++224!!"5t<5rc(V^8dQhR\RR/#rPrQ)rs"rrr`s$$$4$rc\V4p\W\W4,4\V4\ V4\ V4\ W4\V4\V4R#)aHApply environment variable overrides to *config*. Order: plugin platforms' declared env rows, then the core-only rows (api_server, webhook, msgraph_webhook; each touches only its own platform), then the registry enable pass, relay disabling (needs every platform's final ``enabled``), and the marker scrub, which must be last. N) rrrr`rirxrrr)rDrs& r_apply_env_overridesr`sP)0G2H2Y(YZ VV%f6 6NF#rchV^8dQh/^\9d \;R&^\9d \;R&#)rr)r)__conditional_annotations__rrz)rs"rrrs8@&%#%AHIr)r).r__doc__loggingr+typingrgateway.configrrrrrrr r"r r r utilsr getLoggerr/r^rr)rrr%r4r@rNr`rirxrrrrrrrrrrrr)rs@rrs =<!   + , !$%  NN*! &eEJY]8@ dp" =&*Z  ( N Y,(^= $r