߲jFdZddlmZddlZddlmZmZmZddlm Z dddZ y) aProfile-scoped reads of the ``HERMES_*`` tuning settings cron honours from ``.env``. A standalone ``hermes -p X gateway run`` loads X's ``.env`` into ``os.environ``, so a bare ``os.getenv("HERMES_CRON_TIMEOUT")`` is X's value. Under ``gateway.multiplex_profiles`` the same tick runs inside the default profile's process, where ``os.environ`` holds the DEFAULT profile's ``.env``. With a secret scope installed (job run + delivery) the scope is authoritative; the tick loop itself (due-job scan, pool sizing) runs under the profile's home override only, so the setting is read from that home's ``.env``. Outside multiplex the read is the plain environ. ) annotationsN)current_secret_scopeis_multiplex_active load_env_file)get_hermes_homectstj|xs|St}|t t dz }|j |}||St|S)Nz.env)rosgetenvrrrgetstr)namedefaultscopevalues 6/home/ubuntu/.hermes/hermes-agent/cron/env_settings.pycron_env_settingrsZ  yy)') "E }o/&89 IIdOEm73U3))r r rr returnr ) __doc__ __future__rr agent.secret_scoperrrhermes_constantsrrrrrs # WW,4r